-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Conversation
@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 😄 |
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. |
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. |
@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. |
@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 |
There was a problem hiding this 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 👍
There was a problem hiding this 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.
Co-authored-by: Peter Parente <parente@gmail.com>
Co-authored-by: Ayaz Salikhov <mathbunnyru@users.noreply.github.com>
Co-authored-by: Peter Parente <parente@gmail.com>
@parente and @mathbunnyru thanks a lot for your help and advices. |
Parce que vous êtes de Toulouse, je pense que vous parlez français bien et je viens de répondre en français. |
@mathbunnyru you're right and your french is better than my english 🤣 . |
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. |
There was a problem hiding this comment.
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.
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
JUPYTER_ENABLE_LAB
: Jupyter Lab is launched (no change).I've written a test that checks this behavior.
Best