-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Broken Python venv selection #22267
Comments
@quen-de You probably need to clear the cache. Please run the |
If that doesn't help please provide the debug logs which can help diagnose the issue:
Output for
|
Hi @karthiknadig , @karrtikr , thank you for your answer. It looks like clearing the cache worked, I got met with an "invalid virtual environment" for all my projects, and after re-specifying the path to the correct binary, everything was fine. Sorry that I cannot better pinpoint the causation. |
Type: Bug
Selecting a venv either globally or per project doesn't change VS Code's behavior: the default system-wide python binary is always used, in every project.
It happened after I killed a terminal running a frozen python script. Relaunching VS Code or reinstalling the Python module didn't solve the issue.
VS Code version: Code 1.83.0 (e7e037083ff4455cf320e344325dacb480062c3c, 2023-10-03T16:12:16.321Z)
OS version: Windows_NT x64 10.0.22621
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Extensions (25)
A/B Experiments
The text was updated successfully, but these errors were encountered: