Jupyter Server
The Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications like Jupyter notebook, JupyterLab, and Voilà.
For more information, read our documentation here.
Installation and Basic usage
To install the latest release locally, make sure you have pip installed and run:
pip install jupyter_server
Jupyter Server currently supports Python>=3.10 on Linux, OSX and Windows.
Versioning and Branches
If Jupyter Server is a dependency of your project/application, it is important that you pin it to a version that works for your application. Jupyter Server follows semantic versioning: major versions may include breaking API changes, minor versions add functionality in a backwards-compatible way, and patch versions contain backwards-compatible bug fixes.
Maintenance branches are kept for prior major release lines (e.g. 1.x). The main branch always reflects the latest un-released version.
To see the changes between releases, checkout the CHANGELOG.
Usage - Running Jupyter Server
Running in a local installation
Launch with:
jupyter server
Testing
See CONTRIBUTING.
Contributing
If you are interested in contributing to the project, see CONTRIBUTING.rst.
Team Meetings and Roadmap
- When: Thursdays 8:00am, Pacific time
- Where: Jovyan Zoom
- What:
See our tentative roadmap here.
About the Jupyter Development Team
The Jupyter Development Team is the set of all contributors to the Jupyter project. This includes all of the Jupyter subprojects.
The core team that coordinates development on GitHub can be found here: https://github.com/jupyter/.
Our Copyright Policy
Jupyter uses a shared copyright model. Each contributor maintains copyright over their contributions to Jupyter. But, it is important to note that these contributions are typically only changes to the repositories. Thus, the Jupyter source code, in its entirety is not the copyright of any single person or institution. Instead, it is the collective copyright of the entire Jupyter Development Team. If individual contributors want to maintain a record of what changes/contributions they have specific copyright on, they should indicate their copyright in the commit message of the change, when they commit the change to one of the Jupyter repositories.
With this in mind, the following banner should be used in any source code file to indicate the copyright and license terms:
# Copyright (c) Jupyter Development Team.
# Distributed under the terms of the Modified BSD License.
8 maintainers
Release files for jupyter-server 2.21.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jupyter_server-2.21.0.tar.gz | 760.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyter_server-2.21.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / jupyter_server-2.21.0.tar.gz
| Download URL | jupyter_server-2.21.0.tar.gz |
|---|---|
| Size | 760.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70d9a1883f57d3576ea17f4ce061ec1a7aad7ef388d00428cfb7f5e4f0022271
|
|
BLAKE2b-256 checksum How to use checksums |
cfe063b481d5b21f81fe23173dfc9eb25629fa1bc174fdc4a2c19d09c1ff8124
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / jupyter_server-2.21.0-py3-none-any.whl
| Download URL | jupyter_server-2.21.0-py3-none-any.whl |
|---|---|
| Size | 394.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ae2e5ce5e97268553e25aebe040197455673d925b5fc7995477153318160cf7
|
|
BLAKE2b-256 checksum How to use checksums |
cb8acb97c2b353cb46cced413be8f742fa8fcd3cb1659524f27314494aa94968
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
