tasktree 0.0.21__tar.gz → 0.0.23__tar.gz

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

@@ -27,31 +27,26 @@ jobs:
       uses: astral-sh/setup-uv@v4
 
     - name: Install dependencies
-      run: |
-        uv pip install --system -e ".[dev]"
+      run: uv sync --extra dev
 
     - name: Pre-pull Docker images for E2E tests
       if: runner.os == 'Linux'
-      run: |
-        docker pull alpine:latest
+      run: docker pull alpine:latest
 
     - name: Run unit tests
-      run: |
-        python -m pytest tests/unit/ -v --tb=short
+      run: PYTHONPATH=tests uv run pytest tests/unit/ --tb=short
 
     - name: Run integration tests
-      run: |
-        python -m pytest tests/integration/ -v --tb=short
+      run: PYTHONPATH=tests uv run pytest tests/integration/ --tb=short
 
     - name: Run E2E Docker tests
       if: runner.os == 'Linux'
-      run: |
-        python -m pytest tests/e2e/ -v --tb=short
+      run: PYTHONPATH=tests uv run pytest tests/e2e/ --tb=short
 
     - name: Test CLI commands
       run: |
-        python -m tasktree.cli --help
-        python -m tasktree.cli --list || true
+        uv run tt --help
+        uv run tt --list || true
 
   lint:
     runs-on: ubuntu-latest
@@ -67,9 +62,7 @@ jobs:
       uses: astral-sh/setup-uv@v4
 
     - name: Install dependencies
-      run: |
-        uv pip install --system -e ".[dev]"
+      run: uv sync --extra dev
 
     - name: Check code can be imported
-      run: |
-        python -c "from tasktree import Executor, Recipe, Task; print('Import successful')"
+      run: uv run python -c "from tasktree import Executor, Recipe, Task; print('Import successful')"

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

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

{tasktree-0.0.21 → tasktree-0.0.23}/CLAUDE.md

@@ -154,6 +154,8 @@ environments:
   env-name:
     default: true  # Make this the default environment
     shell: /bin/bash  # Shell environment
+    preamble: |  # Optional preamble prepended to all commands
+      set -euo pipefail
     # OR
     dockerfile: path/to/Dockerfile  # Docker environment
     context: build-context-dir

tasktree-0.0.21/README.md → tasktree-0.0.23/PKG-INFO

@@ -1,3 +1,20 @@
+Metadata-Version: 2.4
+Name: tasktree
+Version: 0.0.23
+Summary: A task automation tool with incremental execution
+Requires-Python: >=3.11
+Requires-Dist: click>=8.1.0
+Requires-Dist: colorama>=0.4.6
+Requires-Dist: pathspec>=0.11.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: typer>=0.9.0
+Provides-Extra: dev
+Requires-Dist: black>=26.1.0; extra == 'dev'
+Requires-Dist: pytest>=9.0.2; extra == 'dev'
+Requires-Dist: ruff>=0.14.14; extra == 'dev'
+Description-Content-Type: text/markdown
+
 # Task Tree (tt)
 
 [![Tests](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml)
@@ -234,26 +251,26 @@ 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
     cmd: go build -o dist/binary           # Command to execute
 ```
 
+**Task name constraints:**
+- Task names cannot contain dots (`.`) - they are reserved for namespacing imported tasks
+- Example: `build.release` is invalid as a task name, but valid as a reference to task `release` in namespace `build`
+
 ### Commands
 
-**Single-line commands** are executed directly via the configured shell:
+All commands are executed by writing them to temporary script files. This provides consistent behavior and better shell syntax support:
 
 ```yaml
 tasks:
   build:
     cmd: cargo build --release
-```
 
-**Multi-line commands** are written to temporary script files for proper execution:
-
-```yaml
-tasks:
   deploy:
     cmd: |
       mkdir -p dist
@@ -261,7 +278,7 @@ tasks:
       rsync -av dist/ server:/opt/app/
 ```
 
-Multi-line commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
+Commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
 
 Or use folded blocks for long single-line commands:
 
@@ -277,7 +294,7 @@ tasks:
 
 ### Execution Environments
 
-Configure custom shell environments for task execution:
+Configure custom shell environments for task execution. Use the `preamble` field to add initialization code to all commands:
 
 ```yaml
 environments:
@@ -285,17 +302,14 @@ environments:
 
   bash-strict:
     shell: bash
-    args: ['-c']              # For single-line: bash -c "command"
-    preamble: |               # For multi-line: prepended to script
+    preamble: |               # Prepended to all commands
       set -euo pipefail
 
   python:
     shell: python
-    args: ['-c']
 
   powershell:
     shell: powershell
-    args: ['-ExecutionPolicy', 'Bypass', '-Command']
     preamble: |
       $ErrorActionPreference = 'Stop'
 
@@ -324,8 +338,8 @@ tasks:
 4. Platform default (bash on Unix, cmd on Windows)
 
 **Platform defaults** when no environments are configured:
-- **Unix/macOS**: bash with `-c` args
-- **Windows**: cmd with `/c` args
+- **Unix/macOS**: bash
+- **Windows**: cmd
 
 ### Docker Environments
 
@@ -864,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:
@@ -1606,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
@@ -1634,8 +1657,6 @@ tt --init
 ```bash
 # Remove state file (reset task cache)
 tt --clean
-tt --clean-state
-tt --reset
 ```
 
 ### Common Workflows
@@ -1654,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
@@ -1665,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: