Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Problems with the "Select kernel" dialog which pops up when you run a notebook in VSCode.

See original GitHub issue

    @rchiodo  the problem seems to be with the "Select kernel" dialog which pops up when you run a notebook in VSCode.

The list of venvs is incomplete, or it apparently doesn’t see the venv which the current Python interpreter is using in VSCode.
The list of venvs cannot be refreshed.
It doesn’t have an affordance to enter a path.

edit:

There seems to be some condition which triggers the current venv to appear in the picklist for ‘select kernel’. Cannot quite figure out what that is. Have tried installing ipykernel, have tried running jupyter notebook , etc.

_Originally posted by @guidorice in https://github.com/microsoft/vscode-jupyter/issues/5319#issuecomment-1304293783_

Issue Analytics

State:
Created a year ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

DonJayamannecommented, Nov 20, 2022

Same problem for me. Kernel lists only a few virtual environments (and only one created from venv), but in environment list all appear.

This has been fixed in the latest pre-release version of the Juptyer extesnion, Will close this for now, Please install VS Code insiders and the latest pre-release version of Jupyter & Python extension

The list of venvs cannot be refreshed.

Same as previous comment.

It doesn’t have an affordance to enter a path.

This isn’t supported, you can add a path into Python Interpreters and their environments should now automatically show up in Jupyter extension as well.

Closing this as all have been addressed in the latest pre-release version.

1reaction

rchiodocommented, Nov 4, 2022

@guidorice I added a new issue for you.