You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a conversation with @blink1073 this morning,
I looked at traits in NotebookApp that other extensions might depend on. If we turn the NotebookApp into server extension, such traits/configurations won't be seen by other server extensions. This would break those extensions.
Copy-pasted from my comment on the PR to fix this:
Will deprecating and then eventually removing notebook_dir make this incompatible with JupyterHub, and thus prevent jupyter_server from being used as a backend for jupyterhub-singleuser/SingleUserNotebookApp?
After a conversation with @blink1073 this morning,
I looked at traits in
NotebookApp
that other extensions might depend on. If we turn theNotebookApp
into server extension, such traits/configurations won't be seen by other server extensions. This would break those extensions.Here is the full list:
The only trait that causes trouble in JupyterLab is
notebook_dir
. Jupyter server renames this trait toroot_dir
.We may want to add
notebook_dir
to jupyter_server with a deprecation warning.The text was updated successfully, but these errors were encountered: