loongson/pypi/: nbclassic-0.3.1 metadata and description

Homepage Simple index

Jupyter Notebook as a Jupyter Server Extension.

author Jupyter Development Team
author_email jupyter@googlegroups.com
classifiers
  • Intended Audience :: Developers
  • Intended Audience :: System Administrators
  • Intended Audience :: Science/Research
  • License :: OSI Approved :: BSD License
  • Programming Language :: Python
  • Programming Language :: Python :: 3
  • Programming Language :: Python :: 3.6
  • Programming Language :: Python :: 3.7
  • Programming Language :: Python :: 3.8
description_content_type text/markdown
keywords ipython,jupyter
license BSD
platform
  • Linux
  • Mac OS X
  • Windows
provides_extras test
requires_dist
  • jupyter-server (~=1.8)
  • notebook (<7)
  • pytest ; extra == 'test'
  • pytest-tornasync ; extra == 'test'
  • pytest-console-scripts ; extra == 'test'
requires_python >=3.6

Because this project isn't in the mirror_whitelist, no releases from root/pypi are included.

File Tox results History
nbclassic-0.3.1-py3-none-any.whl
Size
18 KB
Type
Python Wheel
Python
3

Jupyter Notebook as a Jupyter Server Extension

Testing nbclassic

NBClassic runs the Jupyter Notebook frontend on the Jupyter Server backend.

This project prepares for a future where JupyterLab and other frontends switch to Jupyter Server for their Python Web application backend. Using this package, users can launch Jupyter Notebook, JupyterLab and other frontends side-by-side on top of the new Python server backend.

Basic Usage

Install from PyPI:

> pip install nbclassic

This will automatically enable the extension in Jupyter Server.

Launch directly:

> jupyter nbclassic

Alternatively, you can run Jupyter Server and visiting the /tree endpoint:

> jupyter server

Further Details

This project also includes an API for shimming traits that moved from NotebookApp in to ServerApp in Jupyter Server. This can be used by applications that subclassed NotebookApp to leverage the Python server backend of Jupyter Notebooks. Such extensions should now switch to ExtensionApp API in Jupyter Server and add NBClassicConfigShimMixin in their inheritance list to properly handle moved traits.

For example, an application class that previously looked like:

from notebook.notebookapp import NotebookApp

class MyApplication(NotebookApp):

should switch to look something like:

from jupyter_server.extension.application import ExtensionApp
from nbclassic.shim import NBClassicConfigShimMixin

class MyApplication(NBClassicConfigShimMixin, ExtensionApp):