with one click
python-debug-execution-911f17
Debug Python script execution failures by capturing full tracebacks and verifying working directory
Menu
Debug Python script execution failures by capturing full tracebacks and verifying working directory
Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.
Incremental audio production with duration mismatch handling, adaptive stem extension, and pre-mix alignment verification
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow
Incremental audio production with duration alignment handling, per-stem verification, and adaptive extension strategies
Step-by-step audio production with per-stem verification, timing alignment, and incremental quality gates
End-to-end audio production workflow with stems, effects, archiving, and verification
| name | python-debug-execution-911f17 |
| description | Debug Python script execution failures by capturing full tracebacks and verifying working directory |
This skill provides a pattern for debugging Python script execution failures. It ensures you capture actual tracebacks instead of opaque errors and verifies the working directory before file operations.
Always run Python scripts with stderr redirected and exit code reported:
python3 script.py 2>&1 ; echo Exit code: $?
This pattern:
2>&1 - Redirects stderr to stdout so all output (including tracebacks) is captured togetherecho Exit code: $? - Reports the exit code to distinguish between successful runs and failuresWhy this matters: Opaque errors without tracebacks make it impossible to identify the root cause. The exit code tells you if the script succeeded (0) or failed (non-zero).
Before any file read/write operations in your Python script, add:
import os
print(f"Current working directory: {os.getcwd()}")
Or for debugging, add at the start of your script:
import os
import sys
# Debug: show execution context
print(f"Script path: {__file__}")
print(f"Working directory: {os.getcwd()}")
print(f"Python version: {sys.version}")
Why this matters: File operations often fail due to incorrect assumptions about the current working directory. Verifying os.getcwd() helps diagnose path-related errors.
# Instead of:
python3 analyze.py
# Use:
python3 analyze.py 2>&1 ; echo Exit code: $?
#!/usr/bin/env python3
import os
import pandas as pd
# Verify execution context
print(f"Working directory: {os.getcwd()}")
# Now safe to do file operations
data_path = "data/input.csv"
print(f"Attempting to read: {data_path}")
# Check if file exists before reading
if os.path.exists(data_path):
df = pd.read_csv(data_path)
print(f"Successfully loaded {len(df)} rows")
else:
print(f"ERROR: File not found at {os.path.abspath(data_path)}")
print(f"Directory contents: {os.listdir('.')}")
#!/usr/bin/env python3
"""Template for debuggable Python scripts."""
import os
import sys
import traceback
def main():
# Debug: execution context
print("=" * 50)
print(f"Script: {__file__}")
print(f"Working directory: {os.getcwd()}")
print(f"Python: {sys.version}")
print("=" * 50)
try:
# Your main logic here
pass
except Exception as e:
print(f"ERROR: {type(e).__name__}: {e}")
traceback.print_exc()
sys.exit(1)
if __name__ == "__main__":
main()
When a Python script fails:
os.getcwd() to confirm file paths are correctos.path.exists() before operationsos.path.abspath() for clarity