Repository files navigation

The Jupyter notebook is a web-based notebook environment for interactivecomputing.

We maintain thetwo 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:jupyter/notebook-team-compass#5 (comment)

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 thejupyter/notebook code base.

To learn more about Notebook v7:https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html

Maintainance and security-related issues are now being addressed in the6.4.x branch.

A6.5.x branch will be soon created and will depend onnbclassic 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 is a language-agnostic HTML notebook application forProject Jupyter. In 2015, Jupyter notebook was released as a part ofThe Big Split™ of the IPython codebase. IPython 3 was the last major monolithicrelease containing both language-agnostic code, such as theIPython notebook,and language specific code, such as theIPython kernel for Python. Ascomputing spans across many languages, Project Jupyter will continue to develop thelanguage-agnosticJupyter notebook in this repo and with the help of thecommunity develop language specific kernels which are found in their owndiscrete repos.

• The Big Split™ announcement
• Jupyter Ascending blog post

You can find the installation documentation for theJupyter platform, on ReadTheDocs.The documentation for advanced usage of Jupyter notebook can be foundhere.

For a local installation, make sure you havepip installed and run:

pip install notebook

Launch with:

jupyter notebook

You need some configuration before starting Jupyter notebook remotely. SeeRunning a notebook server.

SeeCONTRIBUTING.md for how to set up a local development installation.

If you are interested in contributing to the project, seeCONTRIBUTING.md.

This repository is a Jupyter project and follows the JupyterCommunity Guides and Code of Conduct.

• 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

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/.

Jupyter uses a shared copyright model. Each contributor maintains copyrightover their contributions to Jupyter. But, it is important to note that thesecontributions are typically only changes to the repositories. Thus, the Jupytersource code, in its entirety is not the copyright of any single person orinstitution. Instead, it is the collective copyright of the entire JupyterDevelopment Team. If individual contributors want to maintain a record of whatchanges/contributions they have specific copyright on, they should indicatetheir copyright in the commit message of the change, when they commit thechange to one of the Jupyter repositories.

With this in mind, the following banner should be used in any source code fileto indicate the copyright and license terms:

# Copyright (c) Jupyter Development Team.# Distributed under the terms of the Modified BSD License.