설명 없음

Steven Silvester 7d7f68685a Absorb the buildutils into the webpack build 7 년 전
design 430bb828bb Minor updates. 8 년 전
docs 8e17e66930 Update docs 7 년 전
examples 24f65fe326 Update dependency version. 7 년 전
git-hooks 2774f803fa Add correct target as per Steve's feedback 8 년 전
jupyterlab 7d7f68685a Absorb the buildutils into the webpack build 7 년 전
packages f065c364e7 Don't stringify random objects in error message. 7 년 전
scripts 9453af296e Clean up the addsibling logic 7 년 전
test c9182a0a17 Merge pull request #3062 from ian-r-rose/loading_spinner 7 년 전
typings b09d3bc184 fix rendermime package 8 년 전
.gitignore 21c063a9dd Start a placeholder with a goal for the doc 7 년 전
.npmrc 6f37cf0526 Do not install optional npm packages 7 년 전
.travis.yml 30be938e33 Fix sudo spec 7 년 전
CONTRIBUTING.md 2b84de240f Add Typescript Sourcemaps 7 년 전
LICENSE a64dd81b99 removing formatting diff 7 년 전
MANIFEST.in 7d7f68685a Absorb the buildutils into the webpack build 7 년 전
README.md 918cfb0483 added self and added jupyterlab documentation to help package, closes #3036 7 년 전
RELEASE.md ec813a0244 Update release instructions and add dev version 7 년 전
appveyor.yml e9a637487d Build on appveyor as well 7 년 전
environment.yml 799bc3f9b0 Update environment.yml for new binder 8 년 전
jupyter_plugins.png 1baa71ee22 Update demo and add static picture 9 년 전
lerna.json b071371ff4 Cleanup 7 년 전
package.json 3d71bb61a9 Remove indent 7 년 전
pytest.ini 2538987147 Clean up handling of pytest 8 년 전
readthedocs.yml 03f8b536cf change build directory from tutorial to docs 8 년 전
setup.cfg 936e06a006 Model setup.py after nbdime 8 년 전
setup.py 72011e3c1c Bump launcher dep 7 년 전
setupbase.py 7d7f68685a Absorb the buildutils into the webpack build 7 년 전
tslint.json 3b96e98ba0 Use default exports for plugins 8 년 전

README.md

Installation | Documentation | Contributing | License | Team | Getting help |

JupyterLab

Greenkeeper badge

Build Status Documentation Status Google Group

An extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture.

JupyterLab is the next generation user interface for Project Jupyter. It offers all the familiar building blocks of the classic Jupyter Notebook (notebook, terminal, text editor, file browser, rich outputs, etc.) in a flexible and powerful user inteface that can be extended through third party extensions that access our public APIs. Eventually, JupyterLab will replace the classic Jupyter Notebook.

JupyterLab is approaching its beta release in mid 2017. During our pre-beta series of releases, we encourage users and developers to try out JupyterLab and give us feedback. For users, the upcoming beta will be suitable for general usage. For developers, our APIs will continue to change significantly up until the 1.0 release.

For a good overview of JupyterLab, please see this link to a recent talk we gave about JupyterLab at PyData Seattle (2017).


Getting started

Installation

If you use conda, you can install as:

conda install -c conda-forge jupyterlab

If you use pip, you can install it as:

pip install jupyterlab
jupyter serverextension enable --py jupyterlab --sys-prefix

Instructions on how to install the project from the git sources are available in our contributor documentation.

Note: If installing using pip install --user, you must add the user-level bin directory to your PATH environment variable in order to launch jupyter lab.

Running

Start up JupyterLab using:

jupyter lab

JupyterLab will open automatically in your browser. You may also access JupyterLab by entering the notebook server's URL (http://localhost:8888) in the browser.

Prerequisites

Jupyter notebook version 4.3 or later. To check the notebook version:

jupyter notebook --version

Supported runtimes

The runtime versions which are currently known to work:

  • Firefox Latest
  • Chrome Latest
  • Safari Latest

Earlier browser versions may also work, but come with no guarantees.

JupyterLab uses CSS Variables for styling, which is one reason for the minimum versions listed above. IE 11+ or Edge 14 do not support CSS Variables, and are not directly supported at this time. A tool like postcss can be used to convert the CSS files in the jupyterlab/build directory manually if desired.


Documentation

Read our documentation on ReadTheDocs.


Development

Contributing

If you would like to contribute to the project, please read our contributor documentation.

JupyterLab follows the official Jupyter Code of Conduct.

Extensions

JupyterLab can be extended using extensions that are npm packages and use our public APIs. See our documentation for users and developers.

License

We use a shared copyright model that enables all contributors to maintain the copyright on their contributions. All code is licensed under the terms of the revised BSD license.

Team

JupyterLab is part of Project Jupyter and is developed by an open community of contributors. JupyterLab's current maintainers are as follows:

(listed in alphabetical order, with affiliation, and main areas of contribution)

  • Chris Colbert, Continuum Analytics (co-creator, application/low-level architecture, technical leadership, vision, phosphor.js)
  • Afshin Darian, Continuum Analytics (co-creator, settings, inspector, completer, prolific contributions throughout the code base).
  • Jessica Forde, UC Berkeley (demo, documentation)
  • Brian Granger, Cal Poly (co-creator, strategy, vision, management, UI/UX design, architecture).
  • Jason Grout, Bloomberg (co-creator, vision, general development).
  • Cameron Oelsen, Cal Poly (UI/UX design).
  • Fernando Perez, UC Berkeley (co-creator, vision).
  • Ian Rose, UC Berkeley (Real-time collaboration, document architecture).
  • Steven Silvester, Continuum Analytics (co-creator, release management, packaging, prolific contributions throughout the code base).

This list is provided to help provide context about who we are and how our team functions. This team is accompanied by a much larger group of contributors to JupyterLab and Project Jupyter as a whole. If you would like to be listed here, please submit a pull request with your information.


Getting help

We encourage you to ask questions on the mailing list, and you may participate in development discussions or get live help on Gitter.

Resources