Python debugger fails to launch

[dalemyers]

Issue Type: Bug

Starting at some point in the last ~21 hours I became unable to launch the Python debugger. When I try to launch it (either via the play button on the run and debug pane, or with F5) it tries to run the launcher script in the terminal but then silently exists. I see no errors in any output windows other than in the Window one which says "Server[1] disconnected unexpectedly" (as does the developer console).

I've not changed anything about my configuration. I've tried to restart VSCode. I've rebooted my machine. Other Python debugging functionality works, such as debugging Azure functions.

I do see that the Python extension updated in that ~21 hour window though.

Extension version: 2022.0.1814523869
VS Code version: Code 1.64.1 (d6ee99e4c045a6716e5c653d7da8e9ae6f5a8b03, 2022-02-07T17:26:08.977Z)
OS version: Darwin x64 21.2.0
Restricted Mode: No

[karrtikr]

Are you using a conda interpreter? If so, please update conda to the latest version.

[karthiknadig]

Please follow the instructions here to test out and see if the conda you are using works #18436 (comment)

[dalemyers]

I am not using conda.

…

On Wed, 9 Feb 2022 at 20:58, Karthik Nadig ***@***.***> wrote: Please follow the instructions here to test out and see if the conda you are using works #18436 (comment) <#18436 (comment)> — Reply to this email directly, view it on GitHub <#18486 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKMZCTKVQVI67YEE7MXQT3U2LIQ3ANCNFSM5N5S2QEA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[karthiknadig]

@dalemyers Can you share logs from Output > Python tab? Try running the debugger before you share the logs. this way it will capture the command used to launch the debugger.

[dalemyers]

This is the only line:

DAP Server launched with command: /Users/dalemy/.pyenv/versions/3.10.0a6/bin/python /Users/dalemy/.vscode/extensions/ms-python.python-2022.0.1814523869/pythonFiles/lib/python/debugpy/adapter

However, that showed me what the issue is. It's running the pyenv installation rather than the one in the projects virtual environment. I'm not sure why it changed. It's definitely not something I did manually, but switching back to the Python version in the virtual environment solves this issue.