Live process manipulation with Python 3.14's zero overhead debugging interface
summary
Python 3.14 actually lets you run a real script inside a running interpreter via sys.remote_exec, so you can inject debugpy and use the Debug Adapter Protocol to get full IDE breakpoints and inspection on a live FastAPI pod in local Kubernetes without restarting or changing code. Requirements: Python 3.14 in the container, debugpy present, and sys_ptrace enabled. A CLI called wand debug copies attacher/debug scripts, injects debugpy, sets up port‑forwarding, and works in seconds; watch for multi‑process setups and reloads that change PIDs.
AI-written summary · about
chapters (10)
- 0:00Python 3.14 debugging intro
- 1:31Debugging containerized apps
- 4:38sys.remote_exec safety
- 6:44How sys.remote_exec works
- 8:51Debugging with DAP debugpy
- 10:53Security with sys.remote_exec
- 14:03Debug Wand building
- 17:12Debug Wand step by step
- 19:21Attaching to processes gotchas
- 21:46Future possibilities wrap-up
related talks
39mDebugging python applications inside k8s environment
34mDebugging python applications inside k8s environment
32mA new safe external debugger interface for CPython
28mKnocking On A Process’s Door: Introspecting Live Python Processes
30mHow to Create a Great Local Python Development Environment with Docker
52mCombining Embedded and Interactive Python in a Debugger: A Case Study
26mHow to containerize Python applications with Docker
28mWhat makes a Python debugger possible and how can we make it 100x faster