-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to enter the python executable path in kernel picker under Select a Python Environment
#15086
Comments
Thanks for filing this issue, unfortunately entering a path in the kernel picker does not work. |
Select a Python Environment
Hi, I already had picked my venv via the python interpreter picker. Some of my venvs in other folders come up in the kernel picker, but not the one I'm trying to use. For reference, the relative paths (from my workspace folder venv I want: I notice that both the venvs I'm offered in the kernel picker are in foldered named |
Please could you enable logging as follows:
Please do share all of the logs. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Please see below for the debug output. The kernel picker seems to be trying to pick up a deleted folder in my onedrive, which might be causing issues? I never see the
|
I managed to get a workaround for now by changing the Python default interpreter path in settings, this then comes up in the kernel picker |
Duplicate of #15087 |
Type: Bug
Can't enter a pre-existing venv other than the 2 suggested, entering path to venv in "Select a Python Environment" doesn't work, hitting enter does nothing.
VS Code version: Code 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:10.514Z)
OS version: Windows_NT x64 10.0.19045
Modes:
The text was updated successfully, but these errors were encountered: