Go to file
maltegrosse 2cd1551422
ci/woodpecker/push/woodpecker Pipeline was successful Details
init
2023-01-23 20:55:37 +01:00
jupyter-config init 2023-01-23 20:55:37 +01:00
jupyterlab-training init 2023-01-23 20:55:37 +01:00
schema init 2023-01-23 20:55:37 +01:00
src init 2023-01-23 20:55:37 +01:00
style init 2023-01-23 20:55:37 +01:00
.eslintignore init 2023-01-23 20:55:37 +01:00
.eslintrc.js init 2023-01-23 20:55:37 +01:00
.gitignore init 2023-01-23 20:55:37 +01:00
.prettierignore init 2023-01-23 20:55:37 +01:00
.prettierrc init 2023-01-23 20:55:37 +01:00
.stylelintrc init 2023-01-23 20:55:37 +01:00
.woodpecker.yml init 2023-01-23 20:55:37 +01:00
CHANGELOG.md init 2023-01-23 20:55:37 +01:00
LICENSE init 2023-01-23 20:55:37 +01:00
README.md init 2023-01-23 20:55:37 +01:00
RELEASE.md init 2023-01-23 20:55:37 +01:00
install.json init 2023-01-23 20:55:37 +01:00
package.json init 2023-01-23 20:55:37 +01:00
pyproject.toml init 2023-01-23 20:55:37 +01:00
setup.py init 2023-01-23 20:55:37 +01:00
tsconfig.json init 2023-01-23 20:55:37 +01:00
yarn.lock init 2023-01-23 20:55:37 +01:00

README.md

jupyterlab-training

status-badge

Training Data Pipeline

This extension is composed of a Python package named jupyterlab-training for the server extension and a NPM package named jupyterlab-training for the frontend extension.

Requirements

  • JupyterLab >= 3.0

Install

To install the extension, execute:

pip install jupyterlab-training

Uninstall

To remove the extension, execute:

pip uninstall jupyterlab-training

Troubleshoot

If you are seeing the frontend extension, but it is not working, check that the server extension is enabled:

jupyter server extension list

If the server extension is installed and enabled, but you are not seeing the frontend extension, check the frontend extension is installed:

jupyter labextension list

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the jupyterlab-training directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Server extension must be manually installed in develop mode
jupyter server extension enable jupyterlab-training
# Rebuild extension Typescript source after making changes
jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

# Server extension must be manually disabled in develop mode
jupyter server extension disable jupyterlab-training
pip uninstall jupyterlab-training

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named jupyterlab-training within that folder.

Packaging the extension

See RELEASE