Debugger

Stop your program where it matters and look around. Set a breakpoint, step through line by line, and inspect variables and the call stack while everything is paused.

What you can do

• Set a breakpoint by clicking the editor gutter or pressing F9.
• Turn breakpoints on and off, and find them again in the next session, because they are remembered per project.
• Control the run with Continue (F5), Pause (F6), Step Over (F10), Step Into (F11), Step Out (Shift+F11), Restart (Cmd/Ctrl+Shift+F5) and Stop (Shift+F5).
• Inspect the call stack, and expand variables as you need them.
• Add watch expressions.
• Read your program's output, and evaluate expressions in the paused frame, in the Debug Console.
• Debug a notebook cell by setting a breakpoint in it, in the Notebook (.ipynb) editor. Debugging starts with the first breakpoint and ends when you remove the last one.

Getting started

Open a Python file, click the gutter next to a line to set a breakpoint, and press F5. The Run and Debug sidebar shows the Variables, Watch, Call Stack and Breakpoints sections, and the Debug Console is in the bottom panel.

The active file is configured for you. To keep your own launch configurations, add them to .punica/launch.json in your workspace, which takes a subset of the VS Code format along with ${workspaceFolder} and ${file}.

Requirements

• The desktop app. Debugging starts local processes, so it is not available in the browser.
• Python with debugpy installed. The interpreter comes from Python Environments unless a launch configuration names one. When debugpy is missing, the sidebar offers to install it, or to create a virtual environment with it when your Python is managed by the operating system.

Status

• Python is the only language supported today. Go and Node.js debugging are planned and not available yet.