Update 2020-12-27

[romainx]

The JupyterLab version has been kept in 2.2.x since important changes have been made starting at the version 3.0.0 on the way to manage extensions, see the JupyterLab Changelog. The result is that some of the extensions installed in scipy-notebook are not yet compliant. This issue summarizes in a table the extensions currently compliant with the new version.

The upgrade to JupyterLab 3.0.x is detailed in an issue #1207. However a change has been made in order to prepare this migration #1205 and to help users who want to perform the upgrade by themselves to do so.

The following changes have been made.

• base-notebook
  • Changed: Bump notebook
  • Changed: Bump jupyterhub
  • Added: Created a new configuration file jupyter_server_config.py in order to prepare the migration to JupyterLab 3.0.0, see also the documentation Migrating from Notebook Server explaining this change -> fixes [base-notebook] Cannot connect to server after upgrading to Jupyter Lab 3.0.0 #1205
• scipy-notebook
  • Changed: Bump dask
  • Changed: Bump ipywidgets
  • Changed: Bump numba
  • Changed: Bump protobuf
  • Changed: Bump scikit-image
  • Changed: Bump scikit-learn
  • Added: A test to perform a check on each extension jupyter labextension check.
• r-notebook
  • Changed: Bump r-rmarkdown
• tensorflow-notebook
  • Changed: Bump tensorflow
• datascience-notebook
  • Changed: Bump r-rmarkdown

[romainx]

According to the JupyterLab changelog

Extensions can be installed without building JupyterLab with NodeJS
In JupyterLab 3.0, a new recommended way of distributing and installing extensions as Python pip or conda packages is available. Installing such extensions does not require rebuilding JupyterLab and does not require having NodeJS installed. The previous way of distributing extensions as npm packages requiring rebuilding JupyterLab is still available as well. See the documentation for more details.

I'm wondering if we should remove all the old way of installing extensions in scipy-notebook

docker-stacks/scipy-notebook/Dockerfile

Lines 50 to 59 in d113a60

	jupyter nbextension enable --py widgetsnbextension --sys-prefix && \
	# Also activate ipywidgets extension for JupyterLab
	# Check this URL for most recent compatibilities
	# https://github.com/jupyter-widgets/ipywidgets/tree/master/packages/jupyterlab-manager
	jupyter labextension install @jupyter-widgets/jupyterlab-manager@^2.0.0 --no-build && \
	jupyter labextension install @bokeh/jupyter_bokeh@^2.0.0 --no-build && \
	jupyter labextension install jupyter-matplotlib@^0.7.2 --no-build && \
	jupyter lab build -y && \
	jupyter lab clean -y && \
	npm cache clean --force && \

And if we should merge this PR by dropping the support of the extensions that are not working at the moment or if we should wait until their availability ? A compliance table is given here jupyterlab/jupyterlab#9461.

[romainx]

This PR has been modified to rollback to JupyterLab 2.2.x in order to avoid breaking changes regarding extensions for the time being. Its description has been updated, and I think it's ready to merge now. We will perform the move to JupyterLab 3.0.x in a second step.

[romainx]

Need to check with the last update from @mirekphd in #1205 before merging. Turned back this PR into draft. I will take the time to check it (currently I do not have so much time, I will probably do it next week at the latest).

[romainx]

Hello, I've verified and added a basic test to check extensions (we will see how it behaves with JupyterLab 3.0.x).
So everything seems OK for me 🚀 .
@parente please could you have a look before the merge?

[parente]

👋 I left one comment about lab 3.0 and one suggestion inline. I'm pro-actively approving so you can merge when you feel it's ready.

Thanks as always for keeping the images fresh and responding to community questions.

[bollwyvl]

Pretty sure they will both read jupyter_config.json/py