microsoft / microsoft/vscode-python-debugger
Debugging Python code in a venv in WSL always takes two tries
Open
@eleanorjboyd is already working on this.
Since Nov 4, 2025.
triage-needed
- Dominant language
- TypeScript
- Stars
- 181
- Forks
- 126
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 3
Description
Testing #859
I'm using an Ubuntu WSL instance with pwsh as the default terminal profile.
When I debug a file with Python and with the Python Environments extension enabled, the terminal first runs the debugger commands, and then it cancels that command and runs the venv enablement command. As a result, the debugger fails to launch. On the second attempt, the debugger successfully runs the file because it is not intercepted by the venv enablement command. It successfully hits the breakpoint.
First attempt
Second attempt
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.