SHA256 hashes: jupyter-notebook-application-7.0.0-beta.0.tgz: 102ecf782a63fb11393c05e0feb5d9d4370a245b2e47ff5ed5e6746c724d1038 jupyter-notebook-application-extension-7.0.0-beta.0.tgz: 8c7a5b2ed5f9cb5cc4736fd9fb2ddf31bb73cbbb814fabf4b7114f828855cb77 jupyter-notebook-console-extension-7.0.0-beta.0.tgz: d9873d05874c3f4b9609b78010b1d2b045df4887c9d0d46f5f4486345352ff7d jupyter-notebook-docmanager-extension-7.0.0-beta.0.tgz: 894b218e4ceda62e3ad20d1225fa79bce14641a6625520211dff67af27185e79 jupyter-notebook-documentsearch-extension-7.0.0-beta.0.tgz: a524b9d152558af346eff42130e352b55170b2db302bf1bca8489bb63f540b10 jupyter-notebook-help-extension-7.0.0-beta.0.tgz: 82b619a5c75c3b08ff18e4dc11c9befea812d37828fc59e66f3a16754be0c61b jupyter-notebook-lab-extension-7.0.0-beta.0.tgz: 7c51bc5d12acaf968a92ef11ec4eab55b2b75ea837d2eec28d81045f9d4a4a77 jupyter-notebook-notebook-extension-7.0.0-beta.0.tgz: 35f9b7eefda53e9de9d9c897c13a61df5273ac1c6f23c088aec15a17b009d007 jupyter-notebook-terminal-extension-7.0.0-beta.0.tgz: fcdd9e1fd1b11c7301a132bd19a6dbc1d58e9006f5c13dd67eaff457b70f287c jupyter-notebook-tree-7.0.0-beta.0.tgz: 14839ad3928a43bd444166eb0b1a2f9c6d581f667d0c9358d5272ac940a3121d jupyter-notebook-tree-extension-7.0.0-beta.0.tgz: 881a5fc4d8b22976101055046e3b306b57a89a4404b959c6453a0c22083ec62e jupyter-notebook-ui-components-7.0.0-beta.0.tgz: 1edea9a326f83d8f3213ab69c655a89e0d0079e3f75d441a47166d2467c209b8 notebook-7.0.0b0-py3-none-any.whl: a73f295ad0e728d01af316ed04cadb39913da1e77647faf57a3c4f6b3844a303 notebook-7.0.0b0.tar.gz: efb6e3fd91ad20636c615430ddebf4fc3bd56904419bc88f439732945641b2e8
Jupyter Notebook
The Jupyter notebook is a web-based notebook environment for interactive computing.
Maintained versions
We maintain the two most recently released major versions of Jupyter Notebook, Notebook v5 and Classic Notebook v6. After Notebook v7.0 is released, we will no longer maintain Notebook v5. All Notebook v5 users are strongly advised to upgrade to Classic Notebook v6 as soon as possible.
The Jupyter Notebook project is currently undertaking a transition to a more modern code base built from the ground-up using JupyterLab components and extensions.
There is new stream of work which was submitted and then accepted as a Jupyter Enhancement Proposal (JEP) as part of the next version (v7): https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html
There is also a plan to continue maintaining Notebook v6 with bug and security fixes only, to ease the transition to Notebook v7: https://github.com/jupyter/notebook-team-compass/issues/5#issuecomment-1085254000
Notebook v7
The next major version of Notebook will be based on:
- JupyterLab components for the frontend
- Jupyter Server for the Python server
This represents a significant change to the jupyter/notebook
code base.
To learn more about Notebook v7: https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html
Classic Notebook v6
Maintainance and security-related issues are now being addressed in the 6.4.x
branch.
A 6.5.x
branch will be soon created and will depend on nbclassic
for the HTML/JavaScript/CSS assets.
New features and continuous improvement is now focused on Notebook v7 (see section above).
If you have an open pull request with a new feature or if you were planning to open one, we encourage switching over to the Jupyter Server and JupyterLab architecture, and distribute it as a server extension and / or JupyterLab prebuilt extension. That way your new feature will also be compatible with the new Notebook v7.
Jupyter notebook, the language-agnostic evolution of IPython notebook
Jupyter notebook is a language-agnostic HTML notebook application for Project Jupyter. In 2015, Jupyter notebook was released as a part of The Big Split™ of the IPython codebase. IPython 3 was the last major monolithic release containing both language-agnostic code, such as the IPython notebook, and language specific code, such as the IPython kernel for Python. As computing spans across many languages, Project Jupyter will continue to develop the language-agnostic Jupyter notebook in this repo and with the help of the community develop language specific kernels which are found in their own discrete repos.
Installation
You can find the installation documentation for the Jupyter platform, on ReadTheDocs. The documentation for advanced usage of Jupyter notebook can be found here.
For a local installation, make sure you have pip installed and run:
pip install notebook
Usage - Running Jupyter notebook
Running in a local installation
Launch with:
jupyter notebook
Running in a remote installation
You need some configuration before starting Jupyter notebook remotely. See Running a notebook server.
Development Installation
See CONTRIBUTING.md
for how to set up a local development installation.
Contributing
If you are interested in contributing to the project, see CONTRIBUTING.md
.
Community Guidelines and Code of Conduct
This repository is a Jupyter project and follows the Jupyter Community Guides and Code of Conduct.
Resources
- Project Jupyter website
- Online Demo at jupyter.org/try
- Documentation for Jupyter notebook
- Korean Version of Installation
- Documentation for Project Jupyter [PDF]
- Issues
- Technical support - Jupyter Google Group
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.