-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Python environments failing to be found #18478
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
Ok, I found it. Edited into original post. |
Can you include the python output as well? We ask the python extension for the list of interpreters on the machine. That output makes it look like the python extension didn't find any. |
Infinite stream of:
Well, seems like it is not jupyter problem... |
Begging of log |
Okay I'll transfer your issue to the python team. |
Closing as dup of #18437 |
Duplicate didn't help my case. Everything was working fine until last update of VS Code (python extension to be exact) Edit: downgrading to v2021.12.1559732655 fixed problem for me. That means that something is wrong with newest version. Please fix it. I would say that this is more dub of #18436 |
Uh oh!
There was an error while loading. Please reload this page.
Environment data
Expected behaviour
Jupyter should find at least one environment and everything was working fine until it didn't.
Actual behaviour
No environment/kernels available/detected.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
UNKNOWN, just started to not work. I reinstalled and restarted almost everything, only didn't reinstall the whole system.
Started with numpy not having some libraries (with no changes to anything), I reinstalled Anaconda, restarted everything. Anaconda works in Poweshell and loads correctly. I tried every trick to reset and do it right. Nothing worked.
Logs
Output for
Jupyter
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toJupyter
)The text was updated successfully, but these errors were encountered: