Repository navigation
Debugger is making up its own virtualenv location and unable to run #746
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
Activity
rchiodo commentedon Jul 8, 2025
I don't believe this would be a debugpy issue. It's more likely an issue with the Python debugger extension, trying to activate the venv before starting debugging.
Failed to resolveisn't in the debupgy source anywhere.[-]debugpy is making up its own virtualenv location and unable to run[/-][+]Debugger is making up its own virtualenv location and unable to run[/+]eleanorjboyd commentedon Jul 11, 2025
Hello! Can you check to see if you have a "python" logo in your sidebar menu? This would signal if you have the python environments extension, our new extension for handling environments and maybe that is causing the problem? Info here: microsoft/vscode-python-environments#581. Thanks!
NegassaB commentedon Jul 16, 2025