cc454bb0cc
SHA256 hashes: jupyter-notebook-application-7.0.0-alpha.17.tgz: fd0a4bbc197aa47b5ba6e79759306e676abce29962885418f3d2469e838050dd jupyter-notebook-application-extension-7.0.0-alpha.17.tgz: a8bb9e049d8520a7c6d3aa92293d1501e2c028994c8f88a8274ebe50f55fb71e jupyter-notebook-console-extension-7.0.0-alpha.17.tgz: 069fb2ba8d7778739d7357c1359019a77393c4ed2d91e50a76a1547f81c49e47 jupyter-notebook-docmanager-extension-7.0.0-alpha.17.tgz: 54059a403c4eea255d2e1bac118d808e11cd3dc3fe9c6b6c527d3c0c722053fe jupyter-notebook-documentsearch-extension-7.0.0-alpha.17.tgz: eaaaa8daf944b0f7087afc63d88a60e9f62a6efd939bf46a56a907be516eca1a jupyter-notebook-help-extension-7.0.0-alpha.17.tgz: 0f1a8ce109175c31ccf30d324b6e35178b06e82b0e0fc4bf268bfe1dd91b4eea jupyter-notebook-lab-extension-7.0.0-alpha.17.tgz: c887a7c27f5f37ad71b4410368228966c6055432e37a51c1fc15d5b3418a4c66 jupyter-notebook-notebook-extension-7.0.0-alpha.17.tgz: 17cac111ee63a09a685ef2ff955917abb9fbec386620a37c0d680aae4da7bc46 jupyter-notebook-terminal-extension-7.0.0-alpha.17.tgz: 124a73f6b631d64e5c02dbd87bad104bf3b5b7b4ea92e0c067526ff63f2151f5 jupyter-notebook-tree-7.0.0-alpha.17.tgz: a5a348712c99e3b413307b5599982c89e758e4435dd8cc2741ca0bd1154f9f2b jupyter-notebook-tree-extension-7.0.0-alpha.17.tgz: 1a4f8e322cff780cd439b1f5722ef416b46e2c203ca3f680d4da1a70f9fdbeb1 jupyter-notebook-ui-components-7.0.0-alpha.17.tgz: 8ad41bb70995a8dcbc6f64e785d823456e594f6069218b7b20da74e8d66abd0b notebook-7.0.0a17-py3-none-any.whl: 43017968236c163364490ccd0178a68023c9c7d1fbcdaf9118ebcf1c79f37f77 notebook-7.0.0a17.tar.gz: cf2e5855e07a7b8c08efbeae23643deb29814858d26940a772274365f371a343
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.