0f5f3deafa
SHA256 hashes: jupyter-notebook-application-7.0.0-alpha.14.tgz: 67ce18c024592c13b4d584eadcda97d577e54fa1994a04242b780a25457244d2 jupyter-notebook-application-extension-7.0.0-alpha.14.tgz: 7d6ef5b6a90b580366d9213f2b8aa132e8f1999561ef2e66c9d09d7950aca73e jupyter-notebook-console-extension-7.0.0-alpha.14.tgz: 6a782ba056badc366859dabdf152188a0d96a5a41f227541d5c258653d5fff38 jupyter-notebook-docmanager-extension-7.0.0-alpha.14.tgz: 3e212b60db495daa5e5162638c33bd79b7b727fa0d0ffb8a40dce0bbc63306d5 jupyter-notebook-documentsearch-extension-7.0.0-alpha.14.tgz: 30b92eb5a5de4c9f3cc156b4fca848e17323df2141396f29f7cd300918765615 jupyter-notebook-help-extension-7.0.0-alpha.14.tgz: 5732c5549f215976eb3f475745afd010702d3ef7ae4e5b81be40b955b861ac26 jupyter-notebook-lab-extension-7.0.0-alpha.14.tgz: 61a1324c9b76306233531b31101f6de7abede7a369a997e3d603aaea407f9cbf jupyter-notebook-notebook-extension-7.0.0-alpha.14.tgz: 06871b8108a648c3327146885bcdbe595fc6f71e80d3b0f47ae71d7bc07944a6 jupyter-notebook-terminal-extension-7.0.0-alpha.14.tgz: 201e65e5a653933a4388a66d52d7f051cfb4442edb59d8ff24fefa8d0b31d0c7 jupyter-notebook-tree-7.0.0-alpha.14.tgz: 24fea7713c1a8c08feda7ae9d97f02fd3b1d6da42a0064a828a390da82db9817 jupyter-notebook-tree-extension-7.0.0-alpha.14.tgz: f416902b3d034bbe10ec0663ae9404b26d27f751d7bb02e41939a4b8eb5b9dd9 jupyter-notebook-ui-components-7.0.0-alpha.14.tgz: 2aa5b0998b4b03ef7a62eb116b758c03a2a4d0c678dc067cc5bfd30559dfdfea notebook-7.0.0a14-py3-none-any.whl: 4754b3226320cb8ae9d4200b004a8046d4a065c142892b9d45c1ab449ca5024d notebook-7.0.0a14.tar.gz: 101fb64c77d16a5dc66b29a854d32ed735b15c2cec82745f96810d455d0bc3de
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.