Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JupyterLab 3.0 strategy #935

Closed
4 tasks
manics opened this issue Jul 28, 2020 · 6 comments · Fixed by #996
Closed
4 tasks

JupyterLab 3.0 strategy #935

manics opened this issue Jul 28, 2020 · 6 comments · Fixed by #996

Comments

@manics
Copy link
Member

manics commented Jul 28, 2020

Proposed change

Update to JupyterLab 3.0 when it's released. Switch default from notebook to the planned lab classic notebook mode view.

Alternative options

  • Upgrade to JupyterLab 3.0 but keep the default jupyter-notebook view.

Who would use this feature?

Hopefully everyone! This is a follow-on from #724
Related issues:

How much effort will adding it take?

  • Upgrading to JupyterLab 3.0 will require extensions to be updated, but assuming there are no major API changes this should be straightforward and just require bumping versions of dependencies.
  • Switching the default interface will require investigation since the URL needs to change to /doc.

Who can do this work?

Required changes (please edit and update as required)

@SylvainCorlay
Copy link
Collaborator

Update to JupyterLab 3.0 will hopefully reduce a lot the build time for extensions and all, thanks to the webpack module federation.

@manics
Copy link
Member Author

manics commented Oct 28, 2020

Yes, I'm looking forward to it 😄 . From a repo2docker point of view we need to wait until enough current lab extensions have been updated so we don't break too many repositories.

@jtpio
Copy link
Contributor

jtpio commented Oct 28, 2020

There is now some documentation about updating extensions to be compatible with 3.x, as well as using the new extension distribution system (with pip and conda):

https://jupyterlab.readthedocs.io/en/latest/developer/extension_migration_2_3.html

@jtpio
Copy link
Contributor

jtpio commented Dec 17, 2020

Adding a new TODO item, now that jupyter-resource-usage has been published to PyPI:

  • Switch from nbresuse to jupyter-resource-usage

The package includes a prebuilt extension for JupyterLab 3.0 that displays the memory usage as a status bar item. It was originally part of the JupyterLab code base but has now been moved to jupyter-resource-usage (see jupyterlab/jupyterlab#9386 and jupyter-server/jupyter-resource-usage#69 for more info).

@manics
Copy link
Member Author

manics commented Dec 17, 2020

@jtpio Thanks for the note about jupyter-resource-usage, I've copied it to the main description

On a separate note, I've noticed the latest JupyterLab no longer runs on mybinder, going to /lab results in a 404:
https://mybinder.org/v2/gist/manics/922d4e88fefc6d38fccea8cd2097bc28/HEAD?urlpath=%2Flab

@jtpio
Copy link
Contributor

jtpio commented Dec 18, 2020

On a separate note, I've noticed the latest JupyterLab no longer runs on mybinder, going to /lab results in a 404:

It's probably related to jupyter server now requiring tornado>=6.1. It should normally be fixed with jupyterlab==3.0.0rc14 (more info in jupyterlab/jupyterlab#9453 and linked issues and PRs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants