bf42a0c797
SHA256 hashes: jupyter-notebook-application-7.0.0-beta.4.tgz: 18410b23fe964043c82f4d9f9f817ed1bb84fca021053ecd22e938d7f068f7f4 jupyter-notebook-application-extension-7.0.0-beta.4.tgz: d4ad03cc7b52b6cafc9d28fd4dffd463e7eabae5c4952018d49a18bdad4a793a jupyter-notebook-console-extension-7.0.0-beta.4.tgz: 9b7cd9c2a0faf3eeaef62126449f0f669bc842d50bafb6c29c8c85b607d20141 jupyter-notebook-docmanager-extension-7.0.0-beta.4.tgz: 189631a959f4d42dc75eef8e17233e05b6e85b8ecf893fa1da704da11aec9e86 jupyter-notebook-documentsearch-extension-7.0.0-beta.4.tgz: 31a9b5bf79a5ef7ffd93038e6cdad9eb52086e8ab6a65210a6fc01822caddc0b jupyter-notebook-help-extension-7.0.0-beta.4.tgz: 511e905e0440e4a88ce28d52a9203af013f4b06c1909326e63d6bb6ba8403add jupyter-notebook-lab-extension-7.0.0-beta.4.tgz: 900aa72b5e38cd5264011e0eaedce857576e576c0e493939afd1d89f185769f3 jupyter-notebook-notebook-extension-7.0.0-beta.4.tgz: d5d481d4506249191d86dc7b3fbdac960d06782c6eaf6b14ecd525e8b9032310 jupyter-notebook-terminal-extension-7.0.0-beta.4.tgz: 6656cdfbb189422cb66e8d6ae954de5d2a3f6382e3420961f0721a932836a498 jupyter-notebook-tree-7.0.0-beta.4.tgz: 66be755803462965e05344b768ec320b855e57d309f6474c8167b27fd57dbab6 jupyter-notebook-tree-extension-7.0.0-beta.4.tgz: c1a0d96779cc2b5c8ee419beb16684cdab548817f9b2af1bd9e05f091b0c66a3 jupyter-notebook-ui-components-7.0.0-beta.4.tgz: 4a4926380507746188bf9bcb8d003d8175c1907d745b5003a722461d8ccb7394 notebook-7.0.0b4-py3-none-any.whl: b49d88ed1d091f0ab2b1bd940fa2939968f3d9850898b76b9d5985f2019cdd9d notebook-7.0.0b4.tar.gz: 85319fced7a5ad54f33fc4f32bd0b9477b9e5c3da7be1b98abc09559bd685216
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.