Installation | Documentation | Contributing | License | Team | Getting help |
JupyterLab
An extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture.
JupyterLab is the next-generation user interface for Project Jupyter offering all the familiar building blocks of the classic Jupyter Notebook (notebook, terminal, text editor, file browser, rich outputs, etc.) in a flexible and powerful user interface.
JupyterLab can be extended using npm packages that use our public APIs. The prebuilt extensions can be distributed via PyPI, conda, and other package managers. The source extensions can be installed directly from npm (search for jupyterlab-extension) but require an additional build step. You can also find JupyterLab extensions exploring GitHub topic jupyterlab-extension. To learn more about extensions, see the user documentation.
Read the current JupyterLab documentation on ReadTheDocs.
Getting started
Installation
If you use conda, mamba, or pip, you can install JupyterLab with one of the following commands.
- If you use conda:
conda install -c conda-forge jupyterlab
- If you use mamba:
mamba install -c conda-forge jupyterlab
- If you use pip:
pip install jupyterlab
If installing usingpip install --user, you must add the user-levelbindirectory to yourPATHenvironment variable in order to launchjupyter lab. If you are using a Unix derivative (e.g., FreeBSD, GNU/Linux, macOS), you can do this by runningexport PATH="$HOME/.local/bin:$PATH".
For more detailed instructions, consult the installation guide. Project installation instructions from the git sources are available in the contributor documentation.
Installing with Previous Versions of Jupyter Notebook
When using a version of Jupyter Notebook earlier than 5.3, the following command must be run after installing JupyterLab to enable the JupyterLab server extension:
jupyter serverextension enable --py jupyterlab --sys-prefix
Running
Start up JupyterLab using:
jupyter lab
JupyterLab will open automatically in the browser. See the documentation for additional details.
If you encounter an error like "Command 'jupyter' not found", please make sure PATH environment variable is set correctly. Alternatively, you can start up JupyterLab using ~/.local/bin/jupyter lab without changing the PATH environment variable.
Prerequisites and Supported Browsers
The latest versions of the following browsers are currently known to work:
- Firefox
- Chrome
- Safari
See our documentation for additional details.
Getting help
We encourage you to ask questions on the Discourse forum. A question answered there can become a useful resource for others.
Bug report
To report a bug please read the guidelines and then open a Github issue. To keep resolved issues self-contained, the lock bot will lock closed issues as resolved after a period of inactivity. If a related discussion is still needed after an issue is locked, please open a new issue and reference the old issue.
Feature request
We also welcome suggestions for new features as they help make the project more useful for everyone. To request a feature please use the feature request template.
Development
Extending JupyterLab
To start developing an extension for JupyterLab, see the developer documentation and the API docs.
Contributing
To contribute code or documentation to JupyterLab itself, please read the contributor documentation.
JupyterLab follows the Jupyter Community Guides.
License
JupyterLab uses a shared copyright model that enables all contributors to maintain the copyright on their contributions. All code is licensed under the terms of the revised BSD license.
Team
JupyterLab is part of Project Jupyter and is developed by an open community. The maintenance team is assisted by a much larger group of contributors to JupyterLab and Project Jupyter as a whole. JupyterLab falls under the Jupyter Frontends Council.
The team of maintainers includes:
- decision-making contributors listed on the council team members page
- code contributors listed on the contributors graph page
Archival list of maintainers
Prior to transition to the new governance model with the JupyterLab and then Frontends council, these people contributed to and maintained JupyterLab:
- Mehmet Bektas, Netflix (general development, extensions).
- Alex Bozarth, IBM (general development, extensions).
- Eric Charles, Datalayer, (general development, extensions).
- Frédéric Collonval, WebScIT (general development, extensions).
- Martha Cryan, Mito (general development, extensions).
- Afshin Darian, QuantStack (co-creator, application/high-level architecture, prolific contributions throughout the code base).
- Vidar T. Fauske, JPMorgan Chase (general development, extensions).
- Brian Granger, AWS (co-creator, strategy, vision, management, UI/UX design, architecture).
- Jason Grout, Databricks (co-creator, vision, general development).
- Michał Krassowski, Quansight (general development, extensions).
- Max Klein, JPMorgan Chase (UI Package, build system, general development, extensions).
- Gonzalo Peña-Castellanos, QuanSight (general development, i18n, extensions).
- Fernando Perez, UC Berkeley (co-creator, vision).
- Steven Silvester, MongoDB (co-creator, release management, packaging, prolific contributions throughout the code base).
- Jeremy Tuloup, QuantStack (general development, extensions)
- Chris Colbert, Project Jupyter (co-creator, application/low-level architecture, technical leadership, vision, PhosphorJS)
- Jessica Forde, Project Jupyter (demo, documentation)
- Tim George, Cal Poly (UI/UX design, strategy, management, user needs analysis).
- Cameron Oelsen, Cal Poly (UI/UX design).
- Isabela Presedo-Floyd, QuanSight Labs (design/UX).
- Ian Rose, Quansight/City of LA (general core development, extensions).
- Andrew Schlaepfer, Bloomberg (general development, extensions).
- Saul Shanabrook, Quansight (general development, extensions)
Weekly Dev Meeting
We have video conference meetings every week where we discuss what we have been working on and get feedback from one another.
Anyone is welcome to attend, if they would like to discuss a topic or just listen in.
- When: Wednesdays 9:00 AM Pacific Time (USA)
- Where:
jovyanZoom - What: Meeting notes
Notes are archived on GitHub Jupyter Frontends team compass.
Release files for jupyterlab 4.6.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jupyterlab-4.6.4.tar.gz | 28.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyterlab-4.6.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.5 MB
Release files / jupyterlab-4.6.4.tar.gz
| Download URL | jupyterlab-4.6.4.tar.gz |
|---|---|
| Size | 28.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
404f49b081819378524886c9db66dba57a5565981eff885830df1baba3a17df5
|
|
BLAKE2b-256 checksum How to use checksums |
338d995cc142f6083346b35e7d3eadc5a6717ee89ce64ea53577010ac493bc3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / jupyterlab-4.6.4-py3-none-any.whl
| Download URL | jupyterlab-4.6.4-py3-none-any.whl |
|---|---|
| Size | 17.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
15b13f991d3985129c797eb84d9949eeb8b6615e14b444868e642411f2c418b2
|
|
BLAKE2b-256 checksum How to use checksums |
3be4072bc0d3c6d45d414062a06af7ee81c02a2c12d769c358ec9919f9995ffd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
