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

[rchiodo]

    @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 #5319 (comment)

[rchiodo]

@guidorice I added a new issue for you.

[mateo-st]

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

[dat-linux]

What happened to "enter interpreter path" option in the dropdown???

[DonJayamanne]

happened to "enter interpreter path" option in the dropdown???

I'm sorry, but such an option never existed, do you know what version thsi existed int.
Its possible you are referring to the Python Interpreter picker provided by the Python extension.

[DonJayamanne]

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.

[kuntojirohan]

I'm still facing this issue, exactly the same as mentioned by @rchiodo. Any particular fixes gone into the latests releases of the plugins?

[DonJayamanne]

still facing this issue, exactly the same as mentioned b

please could you file a Seagate bug.
or provide more information like the following

• version of extension and vscode
• screenshot
• what exactly is not wishing and what is expected