Replies: 1 comment 1 reply
-
It's possible the activation command for conda is taking too long such that the debugger never had a chance to connect in time (we have seen that happen before), but I will move this over to an issue on debugpy to see if they have a better idea. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
VS Code Version: 1.59.1 (user setup)
OS Version: Windows 10 19H2
Steps to Reproduce:
Install Miniconda3
Install Vscode, python extension, activate conda (base)
Initial settings with default launch.json, run code in the screenshot with breakpoint. the breakpoint is not working
JustMyCode : false is tested. Not working.
Same test on two different clean machine which never installed python and vscode before.
the debug works fine when a virtual environment create with command such as "conda create -n venv python=3.9.6" Apparently it seems the trouble happens when user is activated (base) without any reason.
Question : Is this a normal situation intended?
Beta Was this translation helpful? Give feedback.
All reactions