tasktree 0.0.22__tar.gz → 0.0.23__tar.gz

{tasktree-0.0.22 → tasktree-0.0.23}/.github/workflows/test.yml

@@ -34,14 +34,14 @@ jobs:
       run: docker pull alpine:latest
 
     - name: Run unit tests
-      run: uv run pytest tests/unit/ --tb=short
+      run: PYTHONPATH=tests uv run pytest tests/unit/ --tb=short
 
     - name: Run integration tests
-      run: uv run pytest tests/integration/ --tb=short
+      run: PYTHONPATH=tests uv run pytest tests/integration/ --tb=short
 
     - name: Run E2E Docker tests
       if: runner.os == 'Linux'
-      run: uv run pytest tests/e2e/ --tb=short
+      run: PYTHONPATH=tests uv run pytest tests/e2e/ --tb=short
 
     - name: Test CLI commands
       run: |

{tasktree-0.0.22 → tasktree-0.0.23}/.gitignore

@@ -159,3 +159,5 @@ requirements/*
 
 .athena-cache
 
+.claude/settings.local.json
+

{tasktree-0.0.22 → tasktree-0.0.23}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tasktree
-Version: 0.0.22
+Version: 0.0.23
 Summary: A task automation tool with incremental execution
 Requires-Python: >=3.11
 Requires-Dist: click>=8.1.0
@@ -251,6 +251,7 @@ tasks:
     working_dir: subproject/               # Execution directory (default: project root)
     env: bash-strict                       # Execution environment (optional)
     private: false                         # Hide from --list output (default: false)
+    task_output: all                       # Control task output: all, out, err, on-err, none (default: all)
     args:                                   # Task parameters
       - param1                              # Simple argument
       - param2: { type: path, default: "." }  # With type and default
@@ -877,7 +878,8 @@ tasks:
     inputs: [src/app-{{ var.version }}.c]
     outputs: [build/app-{{ var.version }}.o]
     cmd: gcc src/app-{{ var.version }}.c -o build/app-{{ var.version }}.o
-
+```
+```yaml
 # With self-references - DRY
 tasks:
   build:
@@ -1619,6 +1621,14 @@ tt -o deploy
 # Override environment for all tasks
 tt --env python analyze
 tt -e powershell build
+
+# Control task subprocess output display
+tt --task-output all build     # Show both stdout and stderr (default)
+tt --task-output out test      # Show only stdout
+tt --task-output err deploy    # Show only stderr
+tt --task-output on-err ci     # Show stderr only if task fails
+tt --task-output none build    # Suppress all task output
+tt -O none build               # Short form
 ```
 
 ### Information Commands
@@ -1647,8 +1657,6 @@ tt --init
 ```bash
 # Remove state file (reset task cache)
 tt --clean
-tt --clean-state
-tt --reset
 ```
 
 ### Common Workflows
@@ -1667,6 +1675,194 @@ tt --env python test
 tt --force deploy production
 ```
 
+### Logging Control
+
+Task Tree provides fine-grained control over diagnostic logging verbosity through the `--log-level` flag. This allows you to adjust the amount of information displayed about task execution, from minimal error-only output to detailed trace logging.
+
+**Log Levels:**
+
+```bash
+# Show only fatal errors (malformed task files, missing dependencies)
+tt --log-level fatal build
+
+# Show fatal errors and task execution failures
+tt --log-level error build
+
+# Show errors and warnings (deprecated features, configuration issues)
+tt --log-level warn build
+
+# Show normal execution progress (default)
+tt --log-level info build
+tt build  # Same as above
+
+# Show detailed diagnostics (variable values, resolved paths, environment details)
+tt --log-level debug build
+
+# Show fine-grained execution tracing
+tt --log-level trace build
+```
+
+**Short Form:**
+
+```bash
+tt -L debug build
+tt -L trace test
+```
+
+**Case Insensitive:**
+
+```bash
+tt --log-level INFO build    # Works
+tt --log-level Debug test    # Works
+tt --log-level TRACE deploy  # Works
+```
+
+**Common Use Cases:**
+
+**Debugging Workflows:**
+```bash
+# See variable substitution and resolved paths
+tt --log-level debug deploy production
+
+# See detailed execution steps and internal state
+tt --log-level trace build
+```
+
+**CI/CD Environments:**
+```bash
+# Suppress progress messages, show only errors
+tt --log-level error build test package
+
+# Minimal output for clean build logs
+tt --log-level warn ci
+```
+
+**Normal Development:**
+```bash
+# Default level shows normal execution progress
+tt build test
+```
+
+**Understanding Log Levels:**
+
+- **FATAL** (least verbose): Only unrecoverable errors that prevent execution
+- **ERROR**: Fatal errors plus individual task failures
+- **WARN**: Errors plus warnings about deprecated features or configuration issues
+- **INFO** (default): Normal execution progress messages
+- **DEBUG**: Info plus variable values, resolved paths, environment configuration
+- **TRACE** (most verbose): Debug plus fine-grained execution tracing
+
+Log levels are hierarchical - setting a higher verbosity level (e.g., DEBUG) includes all messages from lower levels (FATAL, ERROR, WARN, INFO).
+
+**Note:** The `--log-level` flag controls Task Tree's own diagnostic messages. It does not affect the output of task commands themselves - use `--task-output` to control task subprocess output (see below).
+
+### Task Output Control
+
+Task Tree provides fine-grained control over task subprocess output through the `--task-output` flag. This allows you to control whether tasks display their stdout, stderr, both, or neither, independent of Task Tree's own diagnostic logging.
+
+**Output Modes:**
+
+```bash
+# Show both stdout and stderr (default)
+tt --task-output all build
+tt -O all build
+tt build  # Same as above
+
+# Show only stdout, suppress stderr
+tt --task-output out build
+tt -O out test
+
+# Show only stderr, suppress stdout
+tt --task-output err build
+tt -O err deploy
+
+# Show stderr only if the task fails (stdout always suppressed)
+tt --task-output on-err build
+tt -O on-err ci
+
+# Suppress all task output
+tt --task-output none build
+tt -O none build
+```
+
+**Case Insensitive:**
+
+```bash
+tt --task-output ALL build    # Works
+tt --task-output Out test     # Works
+tt --task-output ON-ERR ci    # Works
+```
+
+**Common Use Cases:**
+
+**CI/CD Environments:**
+```bash
+# Suppress task output, show only tasktree diagnostics
+tt --log-level info --task-output none build test
+
+# Show errors only if they occur
+tt --log-level error --task-output on-err ci
+```
+
+**Debugging:**
+```bash
+# Show only stderr to focus on warnings/errors
+tt --task-output err build
+
+# Show everything for full visibility
+tt --log-level debug --task-output all build
+```
+
+**Clean Build Logs:**
+```bash
+# Suppress noisy build output, show only tasktree progress
+tt --task-output none build package deploy
+```
+
+**Task-Level Configuration:**
+
+Tasks can specify their own default output behavior in the recipe file:
+
+```yaml
+tasks:
+  # Noisy task - suppress output by default
+  install-deps:
+    task_output: none
+    cmd: npm install
+
+  # Let pytest manage its own output - it's already good at that
+  test:
+    cmd: pytest tests/
+
+  # Don't clutter CI logs with loads of output, unless something goes wrong
+  build:
+    task_output: on-err
+    cmd: cargo build --release
+```
+
+**Understanding Output Modes:**
+
+| Mode | Stdout | Stderr | Notes |
+|------|--------|--------|-------|
+| `all` | ✓ | ✓ | Default behavior, shows everything |
+| `out` | ✓ | ✗ | Good for capturing command results |
+| `err` | ✗ | ✓ | Focus on warnings and errors |
+| `on-err` | ✗ | ✓ (on failure) | Stderr buffered, shown only if task fails |
+| `none` | ✗ | ✗ | Silent execution, useful for noisy tasks |
+
+**Override Behavior:**
+
+- Command-line `--task-output` overrides task-level `task_output` settings for all tasks
+- Task-level `task_output` applies only if no command-line flag is provided
+- Default behavior is `all` if neither is specified
+
+**Important Notes:**
+
+- Task output control is independent of `--log-level` - you can suppress task output while still seeing tasktree diagnostics
+- The `on-err` mode buffers stderr in memory and only displays it if the task fails
+- Output suppression does not affect the task's execution - files are still created, commands still run
+- Task exit codes are always checked regardless of output mode
+
 ## Example: Full Build Pipeline
 
 ```yaml
@@ -1678,6 +1874,7 @@ tasks:
   compile:
     desc: Build application binaries
     outputs: [target/release/app]
+    task_output: "on-err" # We only care about seeing this if it fails.
     cmd: cargo build --release
 
   test-unit:

{tasktree-0.0.22 → tasktree-0.0.23}/README.md

@@ -234,6 +234,7 @@ tasks:
     working_dir: subproject/               # Execution directory (default: project root)
     env: bash-strict                       # Execution environment (optional)
     private: false                         # Hide from --list output (default: false)
+    task_output: all                       # Control task output: all, out, err, on-err, none (default: all)
     args:                                   # Task parameters
       - param1                              # Simple argument
       - param2: { type: path, default: "." }  # With type and default
@@ -860,7 +861,8 @@ tasks:
     inputs: [src/app-{{ var.version }}.c]
     outputs: [build/app-{{ var.version }}.o]
     cmd: gcc src/app-{{ var.version }}.c -o build/app-{{ var.version }}.o
-
+```
+```yaml
 # With self-references - DRY
 tasks:
   build:
@@ -1602,6 +1604,14 @@ tt -o deploy
 # Override environment for all tasks
 tt --env python analyze
 tt -e powershell build
+
+# Control task subprocess output display
+tt --task-output all build     # Show both stdout and stderr (default)
+tt --task-output out test      # Show only stdout
+tt --task-output err deploy    # Show only stderr
+tt --task-output on-err ci     # Show stderr only if task fails
+tt --task-output none build    # Suppress all task output
+tt -O none build               # Short form
 ```
 
 ### Information Commands
@@ -1630,8 +1640,6 @@ tt --init
 ```bash
 # Remove state file (reset task cache)
 tt --clean
-tt --clean-state
-tt --reset
 ```
 
 ### Common Workflows
@@ -1650,6 +1658,194 @@ tt --env python test
 tt --force deploy production
 ```
 
+### Logging Control
+
+Task Tree provides fine-grained control over diagnostic logging verbosity through the `--log-level` flag. This allows you to adjust the amount of information displayed about task execution, from minimal error-only output to detailed trace logging.
+
+**Log Levels:**
+
+```bash
+# Show only fatal errors (malformed task files, missing dependencies)
+tt --log-level fatal build
+
+# Show fatal errors and task execution failures
+tt --log-level error build
+
+# Show errors and warnings (deprecated features, configuration issues)
+tt --log-level warn build
+
+# Show normal execution progress (default)
+tt --log-level info build
+tt build  # Same as above
+
+# Show detailed diagnostics (variable values, resolved paths, environment details)
+tt --log-level debug build
+
+# Show fine-grained execution tracing
+tt --log-level trace build
+```
+
+**Short Form:**
+
+```bash
+tt -L debug build
+tt -L trace test
+```
+
+**Case Insensitive:**
+
+```bash
+tt --log-level INFO build    # Works
+tt --log-level Debug test    # Works
+tt --log-level TRACE deploy  # Works
+```
+
+**Common Use Cases:**
+
+**Debugging Workflows:**
+```bash
+# See variable substitution and resolved paths
+tt --log-level debug deploy production
+
+# See detailed execution steps and internal state
+tt --log-level trace build
+```
+
+**CI/CD Environments:**
+```bash
+# Suppress progress messages, show only errors
+tt --log-level error build test package
+
+# Minimal output for clean build logs
+tt --log-level warn ci
+```
+
+**Normal Development:**
+```bash
+# Default level shows normal execution progress
+tt build test
+```
+
+**Understanding Log Levels:**
+
+- **FATAL** (least verbose): Only unrecoverable errors that prevent execution
+- **ERROR**: Fatal errors plus individual task failures
+- **WARN**: Errors plus warnings about deprecated features or configuration issues
+- **INFO** (default): Normal execution progress messages
+- **DEBUG**: Info plus variable values, resolved paths, environment configuration
+- **TRACE** (most verbose): Debug plus fine-grained execution tracing
+
+Log levels are hierarchical - setting a higher verbosity level (e.g., DEBUG) includes all messages from lower levels (FATAL, ERROR, WARN, INFO).
+
+**Note:** The `--log-level` flag controls Task Tree's own diagnostic messages. It does not affect the output of task commands themselves - use `--task-output` to control task subprocess output (see below).
+
+### Task Output Control
+
+Task Tree provides fine-grained control over task subprocess output through the `--task-output` flag. This allows you to control whether tasks display their stdout, stderr, both, or neither, independent of Task Tree's own diagnostic logging.
+
+**Output Modes:**
+
+```bash
+# Show both stdout and stderr (default)
+tt --task-output all build
+tt -O all build
+tt build  # Same as above
+
+# Show only stdout, suppress stderr
+tt --task-output out build
+tt -O out test
+
+# Show only stderr, suppress stdout
+tt --task-output err build
+tt -O err deploy
+
+# Show stderr only if the task fails (stdout always suppressed)
+tt --task-output on-err build
+tt -O on-err ci
+
+# Suppress all task output
+tt --task-output none build
+tt -O none build
+```
+
+**Case Insensitive:**
+
+```bash
+tt --task-output ALL build    # Works
+tt --task-output Out test     # Works
+tt --task-output ON-ERR ci    # Works
+```
+
+**Common Use Cases:**
+
+**CI/CD Environments:**
+```bash
+# Suppress task output, show only tasktree diagnostics
+tt --log-level info --task-output none build test
+
+# Show errors only if they occur
+tt --log-level error --task-output on-err ci
+```
+
+**Debugging:**
+```bash
+# Show only stderr to focus on warnings/errors
+tt --task-output err build
+
+# Show everything for full visibility
+tt --log-level debug --task-output all build
+```
+
+**Clean Build Logs:**
+```bash
+# Suppress noisy build output, show only tasktree progress
+tt --task-output none build package deploy
+```
+
+**Task-Level Configuration:**
+
+Tasks can specify their own default output behavior in the recipe file:
+
+```yaml
+tasks:
+  # Noisy task - suppress output by default
+  install-deps:
+    task_output: none
+    cmd: npm install
+
+  # Let pytest manage its own output - it's already good at that
+  test:
+    cmd: pytest tests/
+
+  # Don't clutter CI logs with loads of output, unless something goes wrong
+  build:
+    task_output: on-err
+    cmd: cargo build --release
+```
+
+**Understanding Output Modes:**
+
+| Mode | Stdout | Stderr | Notes |
+|------|--------|--------|-------|
+| `all` | ✓ | ✓ | Default behavior, shows everything |
+| `out` | ✓ | ✗ | Good for capturing command results |
+| `err` | ✗ | ✓ | Focus on warnings and errors |
+| `on-err` | ✗ | ✓ (on failure) | Stderr buffered, shown only if task fails |
+| `none` | ✗ | ✗ | Silent execution, useful for noisy tasks |
+
+**Override Behavior:**
+
+- Command-line `--task-output` overrides task-level `task_output` settings for all tasks
+- Task-level `task_output` applies only if no command-line flag is provided
+- Default behavior is `all` if neither is specified
+
+**Important Notes:**
+
+- Task output control is independent of `--log-level` - you can suppress task output while still seeing tasktree diagnostics
+- The `on-err` mode buffers stderr in memory and only displays it if the task fails
+- Output suppression does not affect the task's execution - files are still created, commands still run
+- Task exit codes are always checked regardless of output mode
+
 ## Example: Full Build Pipeline
 
 ```yaml
@@ -1661,6 +1857,7 @@ tasks:
   compile:
     desc: Build application binaries
     outputs: [target/release/app]
+    task_output: "on-err" # We only care about seeing this if it fails.
     cmd: cargo build --release
 
   test-unit:

{tasktree-0.0.22 → tasktree-0.0.23}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tasktree"
-version = "0.0.22"
+version = "0.0.23"
 description = "A task automation tool with incremental execution"
 readme = "README.md"
 requires-python = ">=3.11"

{tasktree-0.0.22 → tasktree-0.0.23}/schema/tasktree-schema.json

@@ -365,6 +365,12 @@
               "description": "If true, task is hidden from --list output but can still be run directly",
               "default": false
             },
+            "task_output": {
+              "type": "string",
+              "enum": ["all", "out", "err", "on-err", "none"],
+              "description": "Emit the specified output type(s) from the task. (all: everything, out: only stdout, err: only stderr: on-err: only stderr and only if the task fails, none: emit nothing). This setting can be over-ridden by specifying the command-line option",
+              "default": "all"
+            },
             "cmd": {
               "type": "string",
               "description": "Shell command to execute. Supports template substitution: {{ arg.name }} for arguments, {{ var.name }} for variables, {{ env.NAME }} for environment variables, {{ dep.task.outputs.name }} for dependency outputs, {{ self.inputs.name }} and {{ self.outputs.name }} for own inputs/outputs, {{ tt.* }} for built-in variables."

{tasktree-0.0.22 → tasktree-0.0.23}/src/tasktree/__init__.py

@@ -1,6 +1,6 @@
 """
 Task Tree - A task automation tool with intelligent incremental execution.
-@athena: 1b4a97c4bc42
+@athena: 1f9043e194aa
 """
 
 try: