Unlike nodejs debugging with VSCode which support auto-attach and doesn't require extra dependencies, setting debugpy up with VSCode can involve some manual steps. 📘 Official Resource: Python Debugging in VS Code and Debugging in Visual Studio Code
If you wish to debug Python inside VSCode, debugpy is the recommended way to go AFAIK, it is the only mainstream Python debugger that supports the Debug Adapter Protocol (DAP), which is how the debugger communicates with VSCode (as well as other IDEs). That should cover everything you need to get a basic Python editing experience up and running in VSCode, but some more advanced features are broken out further in sections below, such as: In the rare cases you might want to tell VSCode to use a different specific interpreter, you can do so via the faultInterpreterPath setting, GUI, or Command Palette -> Python: Select Interpreter.Most virtual environments it will detect automatically (such as.
The Python extension will use a multi-step resolution process to look for a Python interpreter to use with your code.Optional: Use a virtual environment and/or specific interpreter.Open a project or file in VSCode that contains Python code, or create a new one.Install the Python extension pack for VSCode.Install Visual Studio Code (aka VSCode).🔗 Resource: the official docs on using Python with VSCode - 💡 Python Settings Reference Python and VSCode - Quick Start Guide If you are new to VS Code in general, I recommend checking it out.
📄 For general VS Code tips and tricks, visit the parent page of this one.
0 kommentar(er)
