I cannot select a Python 3.8 virtual environment for Jupyter notebook that is running remotely via SSH plugin

Environment data

• VS Code version: XXX

• Jupyter Extension version (available under the Extensions sidebar):

• Python Extension version (available under the Extensions sidebar):

• OS (Windows | Mac | Linux distro) and version: XXX local OS: Mac OSX / remote OS:

$ lsb_release -a
LSB Version:	core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic

$ uname -a Linux ayan 4.15.0-162-generic #170-Ubuntu SMP Mon Oct 18 11:38:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

• Python and/or Anaconda version: XXX

lrwxrwxrwx 1 root root 9 Oct  1 19:43 /SeaExp/mona/venv/dpcc/bin/python -> python3.8

$ /SeaExp/mona/venv/dpcc/bin/python
Python 3.8.0 (default, Feb 25 2021, 22:10:10) 
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 

• Type of virtual environment used (N/A | venv | virtualenv | conda | …): XXX venv (but it doesn’t even allow to select it via pressing enter)
• Jupyter server running: Local | Remote | N/A remote via the SSH extension

^ When I press enter here in above image, nothing happens for change kernel. It keeps using Python 2. ^ I tried activating the virt env inside the Jupyter but no luck obviously.

Expected behaviour

To be able to use my own virt env /SeaExp/mona/venv/dpcc/bin/python here for running Jupyter ( I have no problem doing this for normal Python scripts inside VSCode remote)

Actual behaviour

Keeps using Python 2 for Jupyter ipynb notebooks.

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

1. XXX

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

XXX

as you can see, I have no problem activating or using this Python Virtual Environment inside VSCode for running normal .py scripts.

[IanMatthewHuff]

@monajalal That control actually can’t accept just a path input. When working with python the dropdown selection should show all the possible options, which would be all the Jupyter kernels and Python environments that we detect on that machine.

When you mention your own native python environments do you mean on your machine? If you connect remotely you should just be seeing the python environments installed on that remote box that you are connected to.

[IanMatthewHuff]

Awesome, glad that it’s working for you now.