python-debugpy

Remote debugging for a running Python process uses debugpy to attach to the live application. You configure debugpy to listen on a port, then connect your debugger to begin stepping through the code and inspecting state.

Post-mortem debugging lets you inspect local variables from exception traces after a Python application crashes. It is needed when you want to analyze the exact program state at the moment an error occurred to find the root cause.

Yes, pdb provides an interactive REPL at breakpoints to inspect state and mutate variables locally. You can insert a breakpoint() directly into your source code or launch scripts with pdb to start stepping through execution.

Yes, debugpy enables remote debugging for headless environments by starting with a listen port or attaching to running processes. This allows in-context debugging of Python applications deployed in production-like setups.

The best way to inspect locals after a Python crash is post-mortem debugging. By using pdb or debugpy, you can load the exception trace and interactively examine the local variables at the exact point where the failure occurred.

Yes, remote debugging requires the debugpy package to enable in-process and remote connections. Standard Python pdb is sufficient for local REPL debugging, but debugpy must be installed to attach to running processes or listen on ports.