Open madiazp opened 7 years ago
Possible solution: Preventing packages from updating (pinning)
In response to capgadsx proposal here are the packages that jupyter use:
jupyter in /usr/lib/python3.5/site-packages
notebook in /usr/lib/python3.5/site-packages
nbconvert in /usr/lib/python3.5/site-packages (from jupyter)
ipywidgets in /usr/lib/python3.5/site-packages (from jupyter)
ipykernel in /usr/lib/python3.5/site-packages (from jupyter)
qtconsole in /usr/lib/python3.5/site-packages (from jupyter)
jupyter-console in /usr/lib/python3.5/site-packages (from jupyter)
nbformat in /usr/lib/python3.5/site-packages (from notebook)
ipython-genutils in /usr/lib/python3.5/site-packages (from notebook)
jupyter-client in /usr/lib/python3.5/site-packages (from notebook)
tornado>=4 in /usr/lib64/python3.5/site-packages (from notebook)
terminado>=0.3.3; sys_platform != "win32" in /usr/lib/python3.5/site-packages (from notebook)
jinja2 in /usr/lib64/python3.5/site-packages (from notebook)
traitlets>=4.2.1 in /usr/lib/python3.5/site-packages (from notebook)
jupyter-core in /usr/lib/python3.5/site-packages (from notebook)
mistune!=0.6 in /usr/lib/python3.5/site-packages (from nbconvert->jupyter)
pandocfilters>=1.4.1 in /usr/lib/python3.5/site-packages (from nbconvert->jupyter)
entrypoints>=0.2.2 in /usr/lib/python3.5/site-packages (from nbconvert->jupyter)
pygments in /usr/lib64/python3.5/site-packages (from nbconvert->jupyter)
bleach in /usr/lib/python3.5/site-packages (from nbconvert->jupyter)
testpath in /usr/lib/python3.5/site-packages (from nbconvert->jupyter)
widgetsnbextension~=2.0.0 in /usr/lib/python3.5/site-packages (from ipywidgets->jupyter)
ipython>=4.0.0 in /usr/lib/python3.5/site-packages (from ipywidgets->jupyter)
prompt-toolkit<2.0.0,>=1.0.0 in /usr/lib/python3.5/site-packages (from jupyter-console->jupyter)
jsonschema!=2.5.0,>=2.4 in /usr/lib/python3.5/site-packages (from nbformat->notebook)
python-dateutil>=2.1 in /usr/lib/python3.5/site-packages (from jupyter-client->notebook)
pyzmq>=13 in /usr/lib64/python3.5/site-packages (from jupyter-client->notebook)
ptyprocess in /usr/lib/python3.5/site-packages (from terminado>=0.3.3; sys_platform != "win32"->notebook)
MarkupSafe>=0.23 in /usr/lib64/python3.5/site-packages (from jinja2->notebook)
decorator in /usr/lib/python3.5/site-packages (from traitlets>=4.2.1->notebook)
six in /usr/lib/python3.5/site-packages (from traitlets>=4.2.1->notebook)
html5lib>=0.99999999 in /usr/lib/python3.5/site-packages (from bleach->nbconvert->jupyter)
pexpect; sys_platform != "win32" in /usr/lib/python3.5/site-packages (from ipython>=4.0.0->ipywidgets->jupyter)
setuptools>=18.5 in /usr/lib/python3.5/site-packages (from ipython>=4.0.0->ipywidgets->jupyter)
pickleshare in /usr/lib/python3.5/site-packages (from ipython>=4.0.0->ipywidgets->jupyter)
simplegeneric>0.8 in /usr/lib/python3.5/site-packages (from ipython>=4.0.0->ipywidgets->jupyter)
wcwidth in /usr/lib/python3.5/site-packages (from prompt-toolkit<2.0.0,>=1.0.0->jupyter-console->jupyter)
webencodings in /usr/lib/python3.5/site-packages (from html5lib>=0.99999999->bleach->nbconvert->jupyter)
When updating a package with pip (available for all users) the pip command uninstalled some package that will be deprecated and were needed by the notebook to connect and work with the hub.
This put in evidence that all user can crash their own jupyter notebooks in the hub by modifying their conda package (willing it or not).