Most projects strongly encourage running tests locally before opening a pull request (or before pushing new commits to an existing PR).
When those tests fail, interactive debugging can help you figure out why.
To ensure you have all the needed VSCode extensions, create a new VS Code profile using the “Python” template profile, and activate it. (Advanced users might skip this step, if they know they already have a suitable profile that is active).
Create a local development environment using the “How to create a local environment” guide. (Optional) You can create an environment with VS Code using the Create Environment command.
Activate your environment and install your project in editable mode. Optionally, also install dev requirements, if your project has them. How you do this depends on the project; most will have a section in pyproject.toml listing optional developer dependencies; if so, install them by putting the optional dependencies group in brackets in the pip install command. For example, if the optional dependences are in a group called dev, you would run in a terminal pip install -e .[dev]. If instead the dev dependencies are in a separate requirements file, you would instead do:
pip install -r <path/to/dev-requirements.txt>
pip install -e .Set up your VS Code Python interpreter to use the Python environment using the Python: Select Interpreter command.
Open the Python file you want to debug in VS Code. Familiarize yourself with the Debugger user interface, which you can open by clicking on the Run and Debug icon in the left menu bar.
You can now start debugging. Set Breakpoints by clicking in the gutter (the space to the left of the line numbers) or pressing F9 on the line where you want the debugger to pause execution. You’ll see the breakpoint set when a red dot appears in the gutter.
For more detailed information about debugging in VS Code, refer to the Debug code with Visual Studio Code or the Python debugging in VS Code documentation pages.