Jupyverse
A set of FPS modules implementing a Jupyter server.
Try it online:
- JupyterLab frontend:
- Jupyter Notebook frontend:
Documentation is available here.
Install
From PyPI
Jupyverse can be installed with pip, for instance the following:
pip install "jupyverse[jupyterlab,auth]"
will install jupyverse with the JupyterLab frontend and the auth plugin.
From conda-forge
Jupyverse can be installed with micromamba:
micromamba create -n jupyverse
micromamba activate jupyverse
micromamba install jupyverse fps-jupyterlab fps-auth
Development install
Clone or fork this repository:
git clone https://github.com/jupyter-server/jupyverse.git
cd jupyverse
Then either use uv or pip to install in development mode.
Using uv
Install all plugins in editable mode:
uv venv
for dir in ./api/*; do dirname=$(basename "$dir"); uv pip install -e "jupyverse-$dirname @ ./api/$dirname"; done
for dir in ./plugins/*; do dirname=$(basename "$dir"); uv pip install -e "fps-$dirname @ ./plugins/$dirname"; done
uv pip install --group test -e .
Run tests with:
uv run pytest -v
For testing, all the plugins are installed in the same environment. Jupyverse will automatically start all plugins
registered in the jupyverse.modules entry point. Some of them should be disabled, for instance there should be only
one authentication plugin:
uv run jupyverse \
--disable auth_fief \
--disable auth_jupyterhub \
--disable noauth \
--disable file_watcher_poll \
--disable notebook
Using pip
Using pip sometimes gives more control, for instance if you want to install third-party libraries
in development mode too. It is recommended to create a virtual environment before running the
following commands:
for dir in ./api/*; do dirname=$(basename "$dir"); pip install -e "./api/$dirname"; done
for dir in ./plugins/*; do dirname=$(basename "$dir"); pip install -e "./plugins/$dirname"; done
pip install --group test -e .
Run tests with:
pytest -v
Run jupyverse with:
jupyverse \
--disable auth_fief \
--disable auth_jupyterhub \
--disable noauth \
--disable file_watcher_poll \
--disable notebook
1 maintainer
Metadata
1 maintainer
Release files for jupyverse 0.14.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jupyverse-0.14.18.tar.gz | 5.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyverse-0.14.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / jupyverse-0.14.18.tar.gz
| Download URL | jupyverse-0.14.18.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d82721bb800ce1edef9426006988cee67c4d0a6e212289722f31ff1e1143497
|
|
BLAKE2b-256 checksum How to use checksums |
36bd5c215687179ba8ced4eb42d4e67567216b4a41f828454abfbe70e273c5c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / jupyverse-0.14.18-py3-none-any.whl
| Download URL | jupyverse-0.14.18-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63da35a99d1af8014b11d91cdade57cab38e09a57dca1e49d9bfaf2ee9183767
|
|
BLAKE2b-256 checksum How to use checksums |
dd40f3b64da447f4eb9cf0aa4dbfd0caddc9b5b9ec0d414192abd1e77aedd9a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for jupyverse 0.14.18
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
