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

Jupyter Notebook Deprecation Notice #1209

Merged
merged 6 commits into from
Jan 19, 2021
Merged

Conversation

romainx
Copy link
Collaborator

@romainx romainx commented Jan 8, 2021

Hello,

This is a very first step of the feature #1217 that consists in printing a deprecation notice in the start-notebook.sh.

Here is the new behavior

  • With no option (no specific environment variable): Jupyter Notebook is launched (no change). However a warning message is printed pointing to https://github.com/jupyter/notebook#notice.
  • With JUPYTER_ENABLE_LAB: Jupyter Lab is launched (no change).

I've written a test that checks this behavior.

Best

@romainx romainx marked this pull request as draft January 8, 2021 08:24
@romainx
Copy link
Collaborator Author

romainx commented Jan 8, 2021

@parente could you please share your opinion? I'd like to make sure I'm in the right direction before I go any further and spend more time updating the documentation. Thanks 😄

@Bidek56
Copy link
Contributor

Bidek56 commented Jan 14, 2021

JupyterLab may be popular but I feel it's a giant web app which sucks up a lot of browser resources, hence I stay away from.
Notebook is much closer to other platforms like Databricks or Colab.
If we do end up defaulting to it, please add some docs on how to un-default it. :) Thanks

@3j14
Copy link

3j14 commented Jan 15, 2021

I added some documentation on your personal fork @romainx.

I understand @Bidek56's concerns and I was also thinking that changing the default behavior might result in confusion. But if the old notebook frontend is actually going to be deprecated and to be replaced with jupyterlab-classic, this change will have to come anyway. It might be beneficial to separate some of the documentation for Docker images from before and after the JupyterLab 3.0 transition to avoid confusion.

@romainx
Copy link
Collaborator Author

romainx commented Jan 15, 2021

@jnsdrtlf thank you very much and sorry for not taking the time to look at your contribution. I will do it for sure 😄 . I am waiting for feedback before going any further because I do not have enough knowledge to identify the possible impacts of such a change.

@3j14
Copy link

3j14 commented Jan 15, 2021

@romainx no worries, this (and the transition to JupyterLab 3.0) is a huge change and should not be rushed. While the documentation clearly states that you should always use a tagged version, I can imagine that people tend to use latest even in production environments. This could cause a lot of headaches.

@romainx romainx requested a review from parente January 16, 2021 08:31
@romainx
Copy link
Collaborator Author

romainx commented Jan 18, 2021

@parente I've implement the changes and now this deprecation stream is followed in a dedicated issue #1217.

@romainx romainx requested a review from parente January 18, 2021 06:45
@romainx romainx marked this pull request as ready for review January 18, 2021 06:45
@romainx romainx changed the title [WIP] Switch to JupyterLab by default Switch to JupyterLab by default Jan 18, 2021
@romainx romainx changed the title Switch to JupyterLab by default Jupyter Notebook Deprecation Notice Jan 18, 2021
README.md Show resolved Hide resolved
base-notebook/start-notebook.sh Outdated Show resolved Hide resolved
Copy link
Member

@mathbunnyru mathbunnyru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job keeping up with Jupyter changes, @romainx 👍

README.md Outdated Show resolved Hide resolved
Copy link
Member

@parente parente left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple more wording suggestions for the README as did @mathbunnyru. Thanks for working on this @romainx and being thoughtful about the community of people who use these images.

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
romainx and others added 3 commits January 18, 2021 18:53
Co-authored-by: Peter Parente <[email protected]>
Co-authored-by: Ayaz Salikhov <[email protected]>
Co-authored-by: Peter Parente <[email protected]>
@romainx
Copy link
Collaborator Author

romainx commented Jan 18, 2021

@parente and @mathbunnyru thanks a lot for your help and advices.
Really appreciate working with you guys ❤️.
I will merge it 🎉 .

@romainx romainx mentioned this pull request Jan 18, 2021
3 tasks
@mathbunnyru
Copy link
Member

@parente and @mathbunnyru thanks a lot for your help and advices.
Really appreciate working with you guys ❤️.
I will merge it 🎉 .

Parce que vous êtes de Toulouse, je pense que vous parlez français bien et je viens de répondre en français.
Désolé pour les erreurs 😂
Merci à vous pour tous les efforts que vous donnes aux images 👍
J'aime bien aussi travailler avec vous 🤗

@romainx
Copy link
Collaborator Author

romainx commented Jan 18, 2021

@mathbunnyru you're right and your french is better than my english 🤣 .
Thanks for the message.

@romainx romainx merged commit aec555e into jupyter:master Jan 19, 2021
This can be done by passing the environment variable `JUPYTER_ENABLE_LAB=yes` at container startup,
more information is available in the [documentation](https://jupyter-docker-stacks.readthedocs.io/en/latest/using/common.html#docker-options).

In April 2021 JupyterLab will become the default for all of the Jupyter Docker stack images, however a new environment variable will be introduced to switch back to Jupyter Notebook if needed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@parente I'm not sure that April 2021 gives enough time for folks to adjust to this change. It will likely break anyone who hasn't pinned to a SHA.

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

Successfully merging this pull request may close these issues.

6 participants