-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Cannot Select Python Interpreter #18567
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
Comments
@yq574485585 Please provide the logs as mentioned in the issue template. Output for
|
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
Just formatting your reply as markdown so it's easier to read: Hi, Kartik! The log is following:
Feel free to contact me if you have further needs. Hoping you can help me out! Thank you, @yq574485585https://github.com/yq574485585 Yes, can you please also set python.logging.level to debug in User settings, reload, send us the log again? Thanks! ― |
Same situation is happening at my side. Please ping me if more information is needed on this issue :-) |
me too |
I have the same issue since 2 weeks. I have downgraded the Python extension to version v2021.11.1422169775 but it still shows the error. Also downgraded Pylance to version v2021.12.2 the issue still exists |
Can't select Python Interpreter if directory name has symbol, for example "C:\Workspace\C++" it will fail to find the Python Interpreter, |
However my Python Interpreter directory name doesn' t have any symbol, so it's not the solution for my case. Anyway thanks for your reply :) |
I also tried to downgrade Python extension to old version. My current version is v2021.5.926500501, it can run my code in conda env's interpreter but still shows 'Cannot Select Python Interpreter' and Python is not installed. Very strange. |
I have the same problem.
I hope that help you find the bug. |
OMG...I think I just figured this out. I've been having EXACTLY the same issue. It appears that, not only can you NOT have symbols included within your folder structure relating to your Python Interpreters but that the same ALSO seems to be the case with regards to the Projects folder too!! I had stored my VS Code Explorer projects folder within a root folder named 'C:\01) Data\ [sub folder root to project repository]' I've litterally just moved my VS Code Explorer projects storage directory into a sub folder of my 'C:\Python' interpreter folders called 'Projects' and my problems went away! Comon Microsoft...sort it out!! i notice that the OP seems to have a folder stucture in use called 'd:\000PhD_Work' is all...SURELY it cant be THAT simple!? |
I have this issue and I reported it at first at the vscode's github. |
I'll take it the original bug is now fixed as no response was provided, closing this. Let me know if it hasn't been fixed and we'll be happy to reopen. @thesalmonidae The issue you face is likely due to #18930. |
Issue Type: Bug
VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:28.252Z)
OS version: Windows_NT x64 10.0.18363
Restricted Mode: No
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (6)
A/B Experiments
The text was updated successfully, but these errors were encountered: