thread-order 1.2.4__tar.gz → 1.3.0__tar.gz

{thread_order-1.2.4/thread_order.egg-info → thread_order-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: thread-order
-Version: 1.2.4
+Version: 1.3.0
 Summary: A lightweight framework for running functions concurrently across multiple threads while maintaining a defined execution order.
 Author-email: Emilio Reyes <soda480@gmail.com>
 License-Expression: Apache-2.0
@@ -34,7 +34,7 @@ Requires-Dist: mock; extra == "dev"
 Requires-Dist: radon; extra == "dev"
 Requires-Dist: bandit; extra == "dev"
 Requires-Dist: coverage; extra == "dev"
-Requires-Dist: coverage-badge; extra == "dev"
+Requires-Dist: genbadge[coverage]; extra == "dev"
 Requires-Dist: twine; extra == "dev"
 Provides-Extra: ui
 Requires-Dist: ttkbootstrap>=1.20.1; extra == "ui"
@@ -218,6 +218,30 @@ These appear in `initial_state` and can be processed in your module’s `setup_s
 
 This allows your module to compute initial state based on CLI parameters.
 
+## Custom Logging
+
+If a module defines a `setup_logging()` function, `tdrun` will automatically detect and invoke it during module initialization. This allows the module to configure its own logging behavior in a consistent and structured way while remaining compatible with the execution model.
+
+```Python
+def setup_logging(
+    workers,                    # Effective worker count resolved by CLI
+    verbose=False,              # Enable verbose (debug-level) logging
+    add_stream_handler=False,   # Attach console handler (disabled when progress/viewer active)
+    add_file_handler=False      # Attach file handler when --log is enabled
+):
+```
+
+At runtime, `tdrun` will invoke it as:
+
+```Python
+setup_logging(
+    args.workers,  # effective workers
+    verbose=args.verbose,
+    add_stream_handler=not args.progress and not args.viewer,
+    add_file_handler=args.log,
+)
+```
+
 ### DAG Inspection
 
 Use graph-only mode to inspect dependency structure:

{thread_order-1.2.4 → thread_order-1.3.0}/README.md

@@ -176,6 +176,30 @@ These appear in `initial_state` and can be processed in your module’s `setup_s
 
 This allows your module to compute initial state based on CLI parameters.
 
+## Custom Logging
+
+If a module defines a `setup_logging()` function, `tdrun` will automatically detect and invoke it during module initialization. This allows the module to configure its own logging behavior in a consistent and structured way while remaining compatible with the execution model.
+
+```Python
+def setup_logging(
+    workers,                    # Effective worker count resolved by CLI
+    verbose=False,              # Enable verbose (debug-level) logging
+    add_stream_handler=False,   # Attach console handler (disabled when progress/viewer active)
+    add_file_handler=False      # Attach file handler when --log is enabled
+):
+```
+
+At runtime, `tdrun` will invoke it as:
+
+```Python
+setup_logging(
+    args.workers,  # effective workers
+    verbose=args.verbose,
+    add_stream_handler=not args.progress and not args.viewer,
+    add_file_handler=args.log,
+)
+```
+
 ### DAG Inspection
 
 Use graph-only mode to inspect dependency structure:

{thread_order-1.2.4 → thread_order-1.3.0}/pyproject.toml

@@ -53,7 +53,7 @@ dev = [
     "radon",
     "bandit",
     "coverage",
-    "coverage-badge",
+    "genbadge[coverage]",
     "twine"
 ]
 ui = [

{thread_order-1.2.4 → thread_order-1.3.0}/thread_order/__init__.py

@@ -53,7 +53,7 @@ def __getattr__(name):
 try:
     __version__ = _metadata.version(__name__)
 except _metadata.PackageNotFoundError:
-    __version__ = '1.2.4'
+    __version__ = '1.3.0'
 
 if getenv('DEV'):
     __version__ = f'{__version__}+dev'

{thread_order-1.2.4 → thread_order-1.3.0}/thread_order/cli/app.py

@@ -1,4 +1,3 @@
-import re
 import sys
 import argparse
 import json
@@ -147,20 +146,13 @@ def _setup_output(scheduler, args):
         def on_task_done(name, thread_name, status, count, total):
             _percent = int((count / total) * 100)
             percent = f'{status.value} [{_percent:3d}% ]'
-            base = f'[{_pad_thread_name(thread_name, args.effective_workers)}] {name}' \
-                if thread_name else name
+            base = f'[{thread_name}] {name}' if thread_name else name
             dots = '.' * max(0, 75 - len(base) - len(percent))
             logger.info(f'{base} {dots} {percent}')
 
         scheduler.on_task_done(on_task_done, total)
         return nullcontext()
 
-def _pad_thread_name(name, workers):
-    """ pad thread name numbers with leading zeros for consistent width
-    """
-    width = len(str(workers - 1))
-    return re.sub(r'(\d+)$', lambda m: m.group(1).zfill(width), name)
-
 def _parse_tags_filter(tags):
     """ parse comma-separated tag list into a normalized filter list
     """
@@ -187,7 +179,11 @@ def _build_scheduler_kwargs(args, initial_state, clear_results_on_start, module)
     # prefer module-provided logging hook if available
     setup_logging_function = getattr(module, 'setup_logging', None)
     if callable(setup_logging_function):
-        setup_logging_function(args.effective_workers, args.verbose)
+        setup_logging_function(
+            args.effective_workers,
+            verbose=args.verbose,
+            add_stream_handler=not args.progress and not args.viewer,
+            add_file_handler=args.log)
     else:
         scheduler_kwargs['setup_logging'] = True
         scheduler_kwargs['verbose'] = args.verbose

{thread_order-1.2.4 → thread_order-1.3.0/thread_order.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: thread-order
-Version: 1.2.4
+Version: 1.3.0
 Summary: A lightweight framework for running functions concurrently across multiple threads while maintaining a defined execution order.
 Author-email: Emilio Reyes <soda480@gmail.com>
 License-Expression: Apache-2.0
@@ -34,7 +34,7 @@ Requires-Dist: mock; extra == "dev"
 Requires-Dist: radon; extra == "dev"
 Requires-Dist: bandit; extra == "dev"
 Requires-Dist: coverage; extra == "dev"
-Requires-Dist: coverage-badge; extra == "dev"
+Requires-Dist: genbadge[coverage]; extra == "dev"
 Requires-Dist: twine; extra == "dev"
 Provides-Extra: ui
 Requires-Dist: ttkbootstrap>=1.20.1; extra == "ui"
@@ -218,6 +218,30 @@ These appear in `initial_state` and can be processed in your module’s `setup_s
 
 This allows your module to compute initial state based on CLI parameters.
 
+## Custom Logging
+
+If a module defines a `setup_logging()` function, `tdrun` will automatically detect and invoke it during module initialization. This allows the module to configure its own logging behavior in a consistent and structured way while remaining compatible with the execution model.
+
+```Python
+def setup_logging(
+    workers,                    # Effective worker count resolved by CLI
+    verbose=False,              # Enable verbose (debug-level) logging
+    add_stream_handler=False,   # Attach console handler (disabled when progress/viewer active)
+    add_file_handler=False      # Attach file handler when --log is enabled
+):
+```
+
+At runtime, `tdrun` will invoke it as:
+
+```Python
+setup_logging(
+    args.workers,  # effective workers
+    verbose=args.verbose,
+    add_stream_handler=not args.progress and not args.viewer,
+    add_file_handler=args.log,
+)
+```
+
 ### DAG Inspection
 
 Use graph-only mode to inspect dependency structure:

{thread_order-1.2.4 → thread_order-1.3.0}/thread_order.egg-info/requires.txt

@@ -7,7 +7,7 @@ mock
 radon
 bandit
 coverage
-coverage-badge
+genbadge[coverage]
 twine
 
 [ui]