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
wrong kernel loads in python interactive #2856
Comments
This is because we can't start jupyter in your other environments. We fall back to searching through all of them if we can't start on the one you started with. You can see that with this here:
This means that the testenvironment does not have jupyter installed (or at least findable). |
strange, because it works fine from anaconda prompt.
|
Yeah from your log it looks we're unable to activate any of the conda environments. This may be related to: |
so still a mystery.... |
Dupe of microsoft/vscode-python#5344 |
This is a conda problem not specific to vscode. The following is a reproducible resolution on my computer (windows 10). The catch is that you must specify a unique kernel name otherwise the kernel is called
I had to restart vscode twice to get it to find my new kernel. I hope this helps others because it was a royal PIA. I also hope this gets more robust from anaconda or from the proposals in microsoft/vscode-python#5344 I pieced this together from these sources, in particular the first |
I can't choose the conda kernels. This has always been hit or miss (there was a previous thread I was part of that I couldn't find) but now no matter what it always launches the same kernel.
Environment data
Expected behaviour
I select the conda kernel from the bottom left or from ctrl+shift+p and then launch conda kernel
Actual behaviour
always launches same kernel "plantcv"
Steps to reproduce:
select any kernel from any conda environment
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)vscode-kernel-issue.txt
The text was updated successfully, but these errors were encountered: