Skip to content
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

Jupyter notebooks not using Python in current path #5998

Closed
Tracked by #1122
DonJayamanne opened this issue May 26, 2021 · 5 comments
Closed
Tracked by #1122

Jupyter notebooks not using Python in current path #5998

DonJayamanne opened this issue May 26, 2021 · 5 comments
Labels
bug Issue identified by VS Code Team member as probable bug notebook-getting-started notebook-kernel Kernels issues (start/restart/switch/execution, install ipykernel) upstream-python Blocked on upstream Python Ext

Comments

@DonJayamanne
Copy link
Contributor

DonJayamanne commented May 26, 2021

As a novice user I test & run Jupyter with python thats in my current path.
However when using Jupyter notebooks a different Python interpreter is used hence:

  • I get prompted to install ipykernel (no idea what this is, i'll click ok)
  • After running a cell, i get module not found errors

Suggestion:
For Jupyter notebooks, use Python thats in the current path instead of active interpreter for blank Python notebooks

We don't need to change how Python exension works for this, optionally we could change the active intepreter in the Python extnsion to point to what's in the current path.

@rchiodo
Copy link
Contributor

rchiodo commented Jul 26, 2021

The work on our side here is to not use the 'active' interpreter for a new notebook, but rather the interpreter that is on the path.

@DonJayamanne
Copy link
Contributor Author

Yes & now (changes at our end & Python).

optionally we could change the active intepreter in the Python extnsion to point to what's in the current path.

but wouldn't this confuse existing users, if Python extension uses something else as its active interpter. Today some of the existing Interactive window users know about active interpreter from Python extension, my argument is that new users woudln't know about it.
Not sure what the fix is.

@DonJayamanne
Copy link
Contributor Author

DonJayamanne commented May 3, 2022

Similar issue here microsoft/vscode-python#18178

@DonJayamanne
Copy link
Contributor Author

Looks like the upstream Python issue was closed here microsoft/vscode-python#17205

@DonJayamanne
Copy link
Contributor Author

Closing as a duplicate of #12274

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug notebook-getting-started notebook-kernel Kernels issues (start/restart/switch/execution, install ipykernel) upstream-python Blocked on upstream Python Ext
Projects
None yet
Development

No branches or pull requests

4 participants