microsoft / microsoft/vscode-python-debugger
Debugger is making up its own virtualenv location and unable to run
Open
@eleanorjboyd is already working on this.
Since Jul 11, 2025.
triage-needed
- Dominant language
- TypeScript
- Stars
- 181
- Forks
- 126
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 3
Description
Before creating a new issue, please check the FAQ to see if your question is answered there.
Environment data
- debugpy version: XXX (run
import debugpy; print(debugpy.__version__)if uncertain) - OS and version: Fedora 37
- Python version (& distribution if applicable, e.g. Anaconda): 3.8.18
- Using VS Code or Visual Studio: VS Code
Actual behavior
the debugger looks for an non-existent virtual environment folder /./venv/bin/python and stops execution
Expected behavior
for the debugger to recognize the virtual environment and run without a hitch
Steps to reproduce:
- in launch.json with the new update the "type" value was changed from "python" to "debugpy"
- when trying to run the debugger with F5 or by pressing the play button the below error comes up and stops execution
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.