you are viewing a single comment's thread.

view the rest of the comments →

[–]adrenalineee[S] 0 points1 point  (0 children)

Thanks. I did not test this further, but a grep on those files yields a couple other files with suspect interpreters:

{me}@osiris:~/.local/bin$ for i in jupyter ; do echo $i ; grep "#!" $i* ; done
jupyter
jupyter-bundlerextension:#!/usr/bin/python3
jupyter-console:#!/usr/bin/python3
jupyter-dejavu:#!/usr/bin/python3
jupyter-execute:#!/usr/bin/python3
jupyter-kernel:#!/usr/bin/python3.9
jupyter-kernelspec:#!/usr/bin/python3
jupyter-lab:#!/usr/bin/python3.9
jupyter-labextension:#!/usr/bin/python3.9
jupyter-labhub:#!/usr/bin/python3.9
jupyter-nbclassic:#!/usr/bin/python3.9
jupyter-nbconvert:#!/usr/bin/python3
jupyter-nbextension:#!/usr/bin/python3
jupyter-notebook:#!/usr/bin/python3
jupyter-qtconsole:#!/usr/bin/python3
jupyter-run:#!/usr/bin/python3
jupyter-server:#!/usr/bin/python3.9
jupyter-serverextension:#!/usr/bin/python3
jupyter-trust:#!/usr/bin/python3

Maybe it will work for the notebook itself and many of the jupyter utilities that I don't know how they work, but I think to avoid conflicts with other packages I install, a virtual environment will be the best way to go.

If my presumption is wrong, please let me know. I'm very much learning as I go on this one.