multiCMD 1.19__tar.gz → 1.20__tar.gz

{multicmd-1.19 → multicmd-1.20}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: multiCMD
-Version: 1.19
+Version: 1.20
 Summary: Run commands simultaneously
 Home-page: https://github.com/yufei-pan/multiCMD
 Author: Yufei Pan
@@ -25,31 +25,24 @@ Dynamic: requires-python
 Dynamic: summary
 
 # multiCMD
-A simple script that is able to issue multiple commands and execute them at the same time locally.
-
-multiCMD can display realtime-ish outputs in color if running multiple commands at the same time.
-
-Can be used in bash scripts for automation actions.
-
-Also able to be imported and act as a wrapper for subprocess.
 
-Use return_object=True with run_commands or run_command to get the Task Object (definition below)
-
-Use quiet=True and wait_for_return=False to create a daemon thread that async updates the return list / objects when return comes 
-
-For each process, it will initialize a thread if using -m/--max_threads > 1
+A simple script that is able to issue multiple commands and execute them at the same time locally.
 
-For each thread, it will use subprocess lib to open a process for the command task
+`multiCMD` can display realtime-ish outputs in color if running multiple commands at the same time.
 
-And it will open two sub threads for processing input and output for the task.
+It can be used in bash scripts for automation actions, and it can also be imported and act as a wrapper for `subprocess`.
 
-They input / output threads will be non-blocking.
+- Use `return_object=True` with `run_commands` or `run_command` to get the Task Object (definition below).
+- Use `quiet=True` and `wait_for_return=False` to create a daemon thread that asynchronously updates the return list / objects when commands finish.
 
-Thus using -t/--timeout will work more reliably.
+For each process, a thread will be initialized if using `-m/--max_threads > 1`.  
+For each thread, `subprocess` is used to open a process for the command task.  
+Two additional threads are opened for processing input and output for the task.  
 
-Note: timeout specifies how many seconds multiCMD will kill the command if NO COMMITTED OUTPUT was detected from the program for this long.
+The input / output threads are non-blocking.  
+Thus, using `-t/--timeout` will work more reliably.
 
-An output line is considered committed if steram hanlder encounters a '\n' or '\r' character.
+**Note:** `timeout` specifies how many seconds `multiCMD` will wait before killing the command if **no committed output** was detected for this duration. An output line is considered committed if the **stream handler** encounters a `\n` or `\r` character.
 
 
 Install via

{multicmd-1.19 → multicmd-1.20}/README.md

@@ -1,29 +1,22 @@
 # multiCMD
-A simple script that is able to issue multiple commands and execute them at the same time locally.
-
-multiCMD can display realtime-ish outputs in color if running multiple commands at the same time.
-
-Can be used in bash scripts for automation actions.
-
-Also able to be imported and act as a wrapper for subprocess.
 
-Use return_object=True with run_commands or run_command to get the Task Object (definition below)
-
-Use quiet=True and wait_for_return=False to create a daemon thread that async updates the return list / objects when return comes 
-
-For each process, it will initialize a thread if using -m/--max_threads > 1
+A simple script that is able to issue multiple commands and execute them at the same time locally.
 
-For each thread, it will use subprocess lib to open a process for the command task
+`multiCMD` can display realtime-ish outputs in color if running multiple commands at the same time.
 
-And it will open two sub threads for processing input and output for the task.
+It can be used in bash scripts for automation actions, and it can also be imported and act as a wrapper for `subprocess`.
 
-They input / output threads will be non-blocking.
+- Use `return_object=True` with `run_commands` or `run_command` to get the Task Object (definition below).
+- Use `quiet=True` and `wait_for_return=False` to create a daemon thread that asynchronously updates the return list / objects when commands finish.
 
-Thus using -t/--timeout will work more reliably.
+For each process, a thread will be initialized if using `-m/--max_threads > 1`.  
+For each thread, `subprocess` is used to open a process for the command task.  
+Two additional threads are opened for processing input and output for the task.  
 
-Note: timeout specifies how many seconds multiCMD will kill the command if NO COMMITTED OUTPUT was detected from the program for this long.
+The input / output threads are non-blocking.  
+Thus, using `-t/--timeout` will work more reliably.
 
-An output line is considered committed if steram hanlder encounters a '\n' or '\r' character.
+**Note:** `timeout` specifies how many seconds `multiCMD` will wait before killing the command if **no committed output** was detected for this duration. An output line is considered committed if the **stream handler** encounters a `\n` or `\r` character.
 
 
 Install via

{multicmd-1.19 → multicmd-1.20}/multiCMD.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: multiCMD
-Version: 1.19
+Version: 1.20
 Summary: Run commands simultaneously
 Home-page: https://github.com/yufei-pan/multiCMD
 Author: Yufei Pan
@@ -25,31 +25,24 @@ Dynamic: requires-python
 Dynamic: summary
 
 # multiCMD
-A simple script that is able to issue multiple commands and execute them at the same time locally.
-
-multiCMD can display realtime-ish outputs in color if running multiple commands at the same time.
-
-Can be used in bash scripts for automation actions.
-
-Also able to be imported and act as a wrapper for subprocess.
 
-Use return_object=True with run_commands or run_command to get the Task Object (definition below)
-
-Use quiet=True and wait_for_return=False to create a daemon thread that async updates the return list / objects when return comes 
-
-For each process, it will initialize a thread if using -m/--max_threads > 1
+A simple script that is able to issue multiple commands and execute them at the same time locally.
 
-For each thread, it will use subprocess lib to open a process for the command task
+`multiCMD` can display realtime-ish outputs in color if running multiple commands at the same time.
 
-And it will open two sub threads for processing input and output for the task.
+It can be used in bash scripts for automation actions, and it can also be imported and act as a wrapper for `subprocess`.
 
-They input / output threads will be non-blocking.
+- Use `return_object=True` with `run_commands` or `run_command` to get the Task Object (definition below).
+- Use `quiet=True` and `wait_for_return=False` to create a daemon thread that asynchronously updates the return list / objects when commands finish.
 
-Thus using -t/--timeout will work more reliably.
+For each process, a thread will be initialized if using `-m/--max_threads > 1`.  
+For each thread, `subprocess` is used to open a process for the command task.  
+Two additional threads are opened for processing input and output for the task.  
 
-Note: timeout specifies how many seconds multiCMD will kill the command if NO COMMITTED OUTPUT was detected from the program for this long.
+The input / output threads are non-blocking.  
+Thus, using `-t/--timeout` will work more reliably.
 
-An output line is considered committed if steram hanlder encounters a '\n' or '\r' character.
+**Note:** `timeout` specifies how many seconds `multiCMD` will wait before killing the command if **no committed output** was detected for this duration. An output line is considered committed if the **stream handler** encounters a `\n` or `\r` character.
 
 
 Install via

{multicmd-1.19 → multicmd-1.20}/multiCMD.py

@@ -12,7 +12,7 @@ import re
 import itertools
 import signal
 
-version = '1.19'
+version = '1.20'
 __version__ = version
 
 __running_threads = []
@@ -194,7 +194,7 @@ def __run_command(task,sem, timeout=60, quiet=False,dry_run=False,with_stdErr=Fa
 			start_time = time.time()
 			outLength = len(task.stdout) + len(task.stderr)
 			time.sleep(0)
-			sleep_time = 1.0e-8 # 10 nanoseconds
+			sleep_time = 1.0e-7 # 100 nanoseconds
 			while proc.poll() is None:  # while the process is still running
 				if task.stop:
 					proc.send_signal(signal.SIGINT)