python-debugpy

Remote debugging a running Python process uses debugpy to attach to a live PID via DAP. You set debugpy.listen on a port like 5678, wait for a client, and inspect state through a DAP-compatible client without restarting the service.

Debugging pytest failures uses pdb post-mortem to examine the crashing frame and its local variables. You drop into a REPL at the failure point via breakpoint() or start the test under pdb to step through and inspect runtime state interactively.

Python remote debugging over DAP works by having debugpy listen on a port like 127.0.0.1:5678 and wait for a client connection. Once a DAP-compatible client attaches, you trigger breakpoints to pause execution and inspect local variables remotely.

Yes, pdb supports post-mortem inspection to examine variables after an unhandled exception. It drops you into a REPL at the exact crashing frame, allowing you to inspect local state and diagnose the defect without modifying code.

pdb provides interactive local debugging via breakpoint-driven REPL inspection in the terminal, while debugpy enables remote and headless debugging over DAP. Use debugpy for long-lived services or subprocesses where restarting is difficult, and pdb for local bug isolation.