e78f05b5f6
SHA256 hashes: jupyter-notebook-application-7.0.0-alpha.18.tgz: 7429a90998f35085aadb76209372eda9dd724dae5d37920f1bd408f7e8a21e9f jupyter-notebook-application-extension-7.0.0-alpha.18.tgz: 5ad1dbf554f5c60b02271b833292f12bcf29e5c0f5545c0da7261265dd428b70 jupyter-notebook-console-extension-7.0.0-alpha.18.tgz: fb191b75147c484bf3f80c1fb70f7ddf0fdca5893f4f5d9eda92261c0812de40 jupyter-notebook-docmanager-extension-7.0.0-alpha.18.tgz: da55183e6c91a872b2808058ff9fcd3c1674ab6091e98d1293247380725854d9 jupyter-notebook-documentsearch-extension-7.0.0-alpha.18.tgz: 31c9e401e830fa0f9b9c874379961f1cdd666a7e59cce91e771b79b081e75d45 jupyter-notebook-help-extension-7.0.0-alpha.18.tgz: e396ac5ea05c903d7a3c813c825ba5428a69592203a9d2781843ce365a755b82 jupyter-notebook-lab-extension-7.0.0-alpha.18.tgz: 29a92b4d6f1bde0b83c11f47decc8ad09dd8b4d9fa5b59ed056eabc8065aefe4 jupyter-notebook-notebook-extension-7.0.0-alpha.18.tgz: 0de2251e846eae92f496cfee43cbb232e81b172f296cdca953092218b7728149 jupyter-notebook-terminal-extension-7.0.0-alpha.18.tgz: 47ba30ad9a52788e55e77c77935e537054e0540b580c5646e2d7b6f194597a6a jupyter-notebook-tree-7.0.0-alpha.18.tgz: e5e1c73d6975681acf424b95d7dcce1fdce04acbfa613b5266edc6a64212c823 jupyter-notebook-tree-extension-7.0.0-alpha.18.tgz: 8dcc04b6bc9878051ac17e5d09cac21da6b978a447a6163b7018e13eb6e83c9d jupyter-notebook-ui-components-7.0.0-alpha.18.tgz: b8caf1fc39584dc7bbb2ac739b327de82f4fc366795308a008e157ec8fec8220 notebook-7.0.0a18-py3-none-any.whl: 17d36528151e0b0e1bf318d2944520f98f08be2860d247c556185ea2bab6d5de notebook-7.0.0a18.tar.gz: 3c1fb8d2a6087b3f043715679338ae2c7fd51b99405ec9acb22b28a254f90741
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.