-
Notifications
You must be signed in to change notification settings - Fork 300
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
Selected Kernel does not point to the right interpreter #5489
Comments
Please could you provide the following information:
|
I think I see the same issue: Version: 1.55.2 (system setup) With venv selected - Jupyter Notebook output:
Command line - same venv activated:
|
@bardal Thanks for the feedback:
I'm sorry you're running into this and would appreciate the replying with the above info, I'd like to unblock you and others running into this. |
I am loading a .ipynb in Visual Studio Code - not sure if that means notebooks or interactive window! Jupyter Cell: 3.8.6 (tags/v3.8.6:db45529, Sep 23 2020, 15:52:53) [MSC v.1927 64 bit (AMD64)] I selected reporting_env as the kernel Screenshot and Jupyter output panel screenshot: |
Thanks for the information,
This is a notebook. Thanks |
reporting_env is a standard Python venv (not conda). |
Thanks for providing the information. |
Unfortunately this is on a work PC so I won't be able to install VS Code
Insiders.
…On Mon, 26 Apr 2021 at 18:04, Don Jayamanne ***@***.***> wrote:
@bardal <https://github.com/bardal> Thanks for the information
Please could you do me yet another favor:
- Please install VS Code Insiders
- Install the Jupyter extension
- Open the same notebook and try this agaon
- Once again, please provide the logs & the screenshot.
FYI - In VS Code Insiders, you'll get the new Notebook UI & I believe this
has been resolved there (See here for more information
https://devblogs.microsoft.com/python/notebooks-are-getting-revamped/).
Thanks again for your help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5489 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLXLESXD24X6OH2YKVBFWDTKWMJ3ANCNFSM42ZWDDFA>
.
|
Originally reported by @muser840
#5214 (comment)
Just to confirm that Jupyter uses the wrong python, which is confirmed by
For me the output of the above prints:
It should be the same! These is some mess with switching between python versions by the extension. Somehow switching to old and already deleted environments make it work. That makes extension totally unusable...
The problem is present on versions:
v2021.5.702919634
v2021.6.732501275
update: sometimes it randomly starts to work...
The text was updated successfully, but these errors were encountered: