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

Make jupyterlab_server optional #11101

Open
davidbrochart opened this issue Sep 17, 2021 · 3 comments
Open

Make jupyterlab_server optional #11101

davidbrochart opened this issue Sep 17, 2021 · 3 comments

Comments

@davidbrochart
Copy link
Contributor

Problem

JupyterLab currently depends on jupyterlab server. For alternative servers to the JupyterLab frontend, such as jupyverse, this dependency is really not necessary, and makes the installation more problematic.

Proposed Solution

jupyterlab_server should either be an optional dependency, that would be installed e.g. with:

pip install jupyterlab[jupyter_server]  # would install jupyterlab_server

or we could keep it as the default server (i.e. jupyterlab_server would be installed when pip install jupyterlab), but it wouldn't be installed when another server is specified:

pip install jupyterlab[jupyverse]  # would not install jupyterlab_server, but would install jupyverse instead
@jtpio
Copy link
Member

jtpio commented Sep 21, 2021

Thanks @davidbrochart for opening this 👍

It would indeed be great if JupyterLab could work without the full set of endpoints exposed by jupyterlab_server. This would also make it easier to build custom distributions (both server side with jupyverse and client side).

Linking to jupyterlab/jupyterlab_server#167 as somehow related.

Adding to the 4.0 milestone for consideration as this might bring some breaking changes.

@linlol
Copy link
Contributor

linlol commented Mar 11, 2024

How about also make a traitlet config to select jupyter _server/jupyverse

@krassowski krassowski modified the milestones: 4.2.0, 4.3.0 May 7, 2024
@krassowski krassowski removed this from the 4.3.0 milestone Aug 14, 2024
@krassowski
Copy link
Member

Clearing the milestone as the associated PR was closed #12625 (comment), we can revisit if we find a backward compatible way to solve this.

Maybe jupyter-server/team-compass#11 could be the ultimate solution here.

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.

5 participants