Ei kuvausta

Jason Grout 6eb4fb03fe Yarn should be available when lerna is run, and the publish command should be non-interactive. 7 vuotta sitten
buildutils f34b41d645 Merge remote-tracking branch 'origin/master' into csvoffset 7 vuotta sitten
design 430bb828bb Minor updates. 8 vuotta sitten
dev_mode f24da8a72c ansi_up 3.0 7 vuotta sitten
docs 12ec5015f2 Fix typo 7 vuotta sitten
examples 0058fb0fe0 Add Vega 3 extension from jupyter-renderers 7 vuotta sitten
git-hooks 2774f803fa Add correct target as per Steve's feedback 8 vuotta sitten
jupyter-config 256b3f77ea Add data_files support (#3546) 7 vuotta sitten
jupyterlab 42c49d1709 Fix python 2/3 issues in semver.py 7 vuotta sitten
packages daf5c22652 Merge pull request #4233 from gnestor/upgrade-vega-embed 7 vuotta sitten
scripts bb6e4bf641 Install travis packages from conda-forge 7 vuotta sitten
tests 75a61d50fe Fix tests. 7 vuotta sitten
.eslintignore d634e52154 wip clean up rendermime rank handling 7 vuotta sitten
.eslintrc.json 28404fd89d Fix uglify (#3496) 7 vuotta sitten
.gitattributes 2a3bc70c04 Upgrade to yarn 1.5.1 7 vuotta sitten
.gitignore ca4f423870 Clean up. 7 vuotta sitten
.travis.yml 8bba57424a Test python 2.7, 3.5, and 3.6. 7 vuotta sitten
.yarnrc c8b319a360 wip update packaging 7 vuotta sitten
CHANGELOG.md aed46ff7f1 Add changelog (#3971) 7 vuotta sitten
CONTRIBUTING.md 38a9c341a9 Merge pull request #3781 from blink1073/node-version-check 7 vuotta sitten
LICENSE a64dd81b99 removing formatting diff 7 vuotta sitten
MANIFEST.in bca554d3f5 Include docs in tarball (#3897) 7 vuotta sitten
README.md d659487d2f Merge pull request #4284 from jzf2101/team-docs 7 vuotta sitten
RELEASE.md 0c4e969f21 Fix doc link. 7 vuotta sitten
appveyor.yml 1bb59caa1e Exit appveyor on failure (#3481) 7 vuotta sitten
clean.py c8b319a360 wip update packaging 7 vuotta sitten
environment.yml 799bc3f9b0 Update environment.yml for new binder 8 vuotta sitten
lerna.json 6eb4fb03fe Yarn should be available when lerna is run, and the publish command should be non-interactive. 7 vuotta sitten
package.json 96c4ccf8b6 Fix jlpm run build on Windows, following pattern used elsewhere in package.json 7 vuotta sitten
pytest.ini c8b319a360 wip update packaging 7 vuotta sitten
readthedocs.yml 03f8b536cf change build directory from tutorial to docs 8 vuotta sitten
setup.cfg 936e06a006 Model setup.py after nbdime 8 vuotta sitten
setup.py 7dec31674b Add a node compatiblity check 7 vuotta sitten
setupbase.py 62d7627c72 Fix data_files handling 7 vuotta sitten
tslint.json 62e33259f7 tslint and nounusedlocals updates 7 vuotta sitten
yarn.lock f24da8a72c ansi_up 3.0 7 vuotta sitten

README.md

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

JupyterLab

Build Status Documentation Status Google Group Join the Gitter Chat Binder

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

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. Eventually, JupyterLab will replace the classic Jupyter Notebook after JupyterLab reaches 1.0.

JupyterLab can be extended using extensions that are npm packages and use our public APIs. You can search for the GitHub topic jupyterlab-extension to find extensions. To learn more about extensions, see our user documentation.

The beta releases are suitable for general usage. For JupyterLab extension developers, the extension APIs will continue to evolve until the 1.0 release.

Read the latest version of our documentation on ReadTheDocs.


Getting started

Installation

You can install JupyterLab using conda, pip, or pipenv.

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

conda

If you use conda, you can install as:

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

pip

If you use pip, you can install it as:

pip install jupyterlab

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.

pipenv

If you use pipenv, you can install it as:

pipenv install jupyterlab
pipenv shell

or from a git checkout:

pipenv install git+git://github.com/jupyterlab/jupyterlab.git#egg=jupyterlab
pipenv shell

When using pipenv, in order to launch jupyter lab, you must activate the project's virtualenv. For example, in the directory where pipenv's Pipfile and Pipfile.lock live (i.e., where you ran the above commands):

pipenv shell
jupyter lab

Installing with Previous Versions of Jupyter Notebook

If you are using a version of Jupyter Notebook earlier than 5.3, then you must also run the following command after installation to enable the JupyterLab server extension:

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

Running

Start up JupyterLab using:

jupyter lab

JupyterLab will open automatically in your browser. See our documentation for additional details.

Prerequisites and Supported Browsers

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

jupyter notebook --version

The latest versions of the following browsers are currently known to work:

  • Firefox
  • Chrome
  • Safari

See our documentation for additional details.


Development

Contributing

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

JupyterLab follows the official Jupyter Code of Conduct.

Extending JupyterLab

To start developing your own extension, see our developers documentation and API docs.

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. Our maintainer team is accompanied by a much larger group of contributors to JupyterLab and Project Jupyter as a whole.


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. Please use our issues page to provide feedback or submit a bug report.