python-debugpy

Python post-mortem debugging uses pdb to inspect the program state exactly where an exception occurred. By dropping into a post-mortem session, you can analyze the traceback, evaluate locals, and identify the crash cause without restarting.

You can drop into pdb on a failing pytest run by using the built-in breakpoint() function or pytest's --pdb flag. This pauses test execution at the failure point to trace execution and inspect local variables interactively.

Python post-mortem analysis uses pdb to inspect the program state exactly where an unhandled exception occurred. This lets you evaluate local variables and trace the failure path immediately after a crash without modifying the code.

Yes, you can attach debugpy to a Python subprocess to inspect its runtime state. This is useful for diagnosing misbehaving workers or daemons where restarting the parent process is impractical.

Use remote-pdb instead of local pdb when debugging long-running services or daemons where terminal access is unavailable. Remote-pdb allows you to attach to a running process over a network to pause and inspect execution safely.