What problem does it solve? Diagnosing Python bugs in tests, scripts, and long-running processes is hard when tracebacks alone don't reveal why values are wrong, and restarting misbehaving daemons or subprocesses to add print statements is slow or impossible. ## Core Features & Use Cases - Interactive pdb debugging: Set breakpoints with breakpoint(), step through code, inspect locals, and run post-mortem analysis on exceptions. - Remote debugging with debugpy: Attach to already-running processes via DAP, or use remote-pdb for a terminal-friendly pdb prompt over a socket. - Pytest integration: Drop into pdb on test failures with --pdb, handling the xdist incompatibility that silently hangs test runs. - Use Case: A gateway subprocess misbehaves in production-like conditions. Add remote_pdb.set_trace() in the suspect handler, trigger the code path, connect with nc 127.0.0.1 4444, and inspect the live call stack and variables without restarting the service. ## Quick Start Add a breakpoint() call at the suspect line in my Python file and walk me through inspecting the variables when execution pauses there.
