VSCode Jupyter loads incorrect version of python

Question

VSCode's Jupyter isn't actually running the version of python that it displays in the lower left of the screen.

Below, it purports to be running 3.9.1, but the output of the cell shows that it is indeed running 3.7.9.

I selected the displayed rl environment via: Select environment to start Jupyter Server.

What doesn't work:

Restarting the Jupyter kernel
Selecting a different environment (they all actually run 3.7.9 regardless of the env's python)

incorrect version of python

Extra info:

Python Output:

> conda --version
> pyenv root
> python3.7 ~/.vscode/extensions/ms-python.python-2020.12.424452561/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 ~/.vscode/extensions/ms-python.python-2020.12.424452561/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3 ~/.vscode/extensions/ms-python.python-2020.12.424452561/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 ~/.vscode/extensions/ms-python.python-2020.12.424452561/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode/extensions/ms-python.python-2020.12.424452561/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~/.local/share/miniconda3/envs/rl/bin/python ~/.vscode/extensions/ms-python.python-2020.12.424452561/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> conda info --json
Starting Pylance language server.
Python interpreter path: ~/.local/share/miniconda3/envs/rl/bin/python
> conda env list
> conda env list

Yes, that last listed interpreter really is v3.9.1:

% ~/.local/share/miniconda3/envs/rl/bin/python --version
Python 3.9.1

Jupyter Output:

User belongs to experiment group 'jupyterTest'
> ~/.local/share/miniconda3/envs/rl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py -c "import ipykernel"
> ~/.local/share/miniconda3/envs/nndl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py -c "import notebook"
> ~/.local/share/miniconda3/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py -c "import ipykernel"
> ~/.local/share/miniconda3/envs/nndl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py -c "import jupyter"
> ~/.local/share/miniconda3/envs/nndl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py jupyter kernelspec --version
> ~/.local/share/miniconda3/envs/nndl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v
> ~/.local/share/miniconda3/envs/nndl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v
> ~/.local/share/miniconda3/envs/nndl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v
> ~/.local/share/miniconda3/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
> ~/.local/share/miniconda3/envs/rl/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
Started kernel Python 3
> ~/.local/share/miniconda3/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2020.12.414227025/pythonFiles/pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v

This final listed python is the incorrect, non-selected version:

% ~/.local/share/miniconda3/bin/python --version
Python 3.7.9

Why is this version being used when the correct ~/.local/share/miniconda3/envs/rl/bin/python is listed immediately above?

Tom Hale · Accepted Answer · 2021-01-04 10:28:54Z

3

What eventually worked for me was:

Close VSCode
In .ipynb pane's top right, change version of Python to the desired conda environment
Start the kernel

Changing the kernel and then restarting it didn't seem to work.

answered Jan 4, 2021 at 10:28

Tom Hale

48.1k43 gold badges207 silver badges275 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Marc Over a year ago

Yes, thanks!!!! I've been banging my head around, every time I was choosing "select interpreter" to change it but it never worked. What's the difference between top right and the interpreter?

Jill Cheng · Accepted Answer · 2021-01-05 01:22:07Z

2

In VSCode, the Python environment of Jupyter notebook is independent, it uses the Python environment we chose last time by default. We can click on "Python3: Idle" in the upper right corner and switch to the Python3.9 environment.

Please reload VSCode after switching the Python environment to make Jupyter reload the corresponding kernel.

edited Jan 5, 2021 at 1:22

answered Dec 30, 2020 at 9:45

Jill Cheng

10.5k1 gold badge24 silver badges30 bronze badges

2 Comments

Tom Hale Over a year ago

Sadly, this is not correct. Extension Python depends on Jupyter: Cannot disable extension 'Jupyter'. Extension 'Python' depends on this. I now have 3.9.1 in both top right and bottom left parts of the screen, but by sys.version output remains unchanged.

Tom Hale Over a year ago

Cheers for pointing out the top right part though, it led to my answer.

user16459765 · Accepted Answer · 2021-07-16 03:38:24Z

0

https://www.it-swarm-vi.com/vi/python/ipynb-nhap-tap-tin-ipynb-khac/1042793988/

!pip install import_ipynb`enter code here`
!pip install ipynb

import import_ipynb
import ipynb

from ipynb.fs.full.tim_folder import tim_folder

answered Jul 16, 2021 at 3:38

user16459765

111 bronze badge

Comments

Don M · Accepted Answer · 2022-11-27 06:34:42Z

0

I've been in situations where I've tried to specify the python version when creating the environment for conda.

conda env create -f environment.yml python={version}

It would usually install the latest version and ignore my command.

To resolve this I activate my environment: conda activate ${env}

Then I install the right version: conda install python=3.9.12 -y

The key or big take away that I gathered is in the VSCode UI it gives me the option to select my kernel environment & it also gives me the path to that environment. When I went in to that directory the python version was not there. So...install it, reboot VScode.

answered Nov 27, 2022 at 6:34

Don M

9861 gold badge10 silver badges27 bronze badges

Collectives™ on Stack Overflow

VSCode Jupyter loads incorrect version of python

4 Answers 4

1 Comment

2 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related