3886790af1
SHA256 hashes: jupyter-notebook-application-7.0.0-alpha.15.tgz: 7b4acdfcd454818bff871d3f059c8b29e93d4e90fdfb166517184670c1f5f08d jupyter-notebook-application-extension-7.0.0-alpha.15.tgz: d3f07eadbc4847cd90abe67cd31920afe40bdc788e746d71d9c8efab0b28beb0 jupyter-notebook-console-extension-7.0.0-alpha.15.tgz: 2d165983ec8ac2b51576d9040cb21200320cb7f06d64dee1aa05bf9bc743634d jupyter-notebook-docmanager-extension-7.0.0-alpha.15.tgz: 8a8e2f928cb07a355f2cdf01016ce5c240ed2f5a82924daf419e0064693b5b0f jupyter-notebook-documentsearch-extension-7.0.0-alpha.15.tgz: 11be1e546a87dccbae8982e2bf46b28236e5a9f9c49d45ca761f4a0a84f04e56 jupyter-notebook-help-extension-7.0.0-alpha.15.tgz: 73d8caee1e0bc8600ad7688c04e8d2ba82efad2927aedc6766f7d437fa7ba728 jupyter-notebook-lab-extension-7.0.0-alpha.15.tgz: f3886e19558a04f2946786b4f3b81d8a00b24fc1c15dbe1142ef24d2f501b571 jupyter-notebook-notebook-extension-7.0.0-alpha.15.tgz: 570c9baff9936dbc43413d6368ab4ce623e7bed127fbfdd495f6b963564a8955 jupyter-notebook-terminal-extension-7.0.0-alpha.15.tgz: 2555ecec5b9a35c2b788067f3b47c8fe968fea28be03e8385cd9d109597b24ec jupyter-notebook-tree-7.0.0-alpha.15.tgz: 46cf4f6c94e61bd3b6eaef3bcbb6d008006f600b3f3b46c78a478fb7eb577e4c jupyter-notebook-tree-extension-7.0.0-alpha.15.tgz: 5637759ed183f8ce8a38cb307a00c1452c5c4d21413273d2693ce153239b7fff jupyter-notebook-ui-components-7.0.0-alpha.15.tgz: 35dd694784ca91042d19662f755f86423e1e4afe74b5976d3c8411330d11cb0b notebook-7.0.0a15-py3-none-any.whl: 1f9bf33bd224dabd430e297f23a634aa2014b5c1de10ae3029ea4fff54098cb3 notebook-7.0.0a15.tar.gz: ab0d9976222e9fd83fab08369ddaa57760dd1657a484652a12692feaddf5c339
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.