Skip to content

Carreau/papyri-lab

Repository files navigation

papyri_lab

Github Actions Status

papyri-lab extension

Binder (Jupyter Lab)

A jupyter lab extension for papyri

This extension is composed of a Python package named papyri_lab for the server extension and a NPM package named papyri-lab for the frontend extension.

Requirements

  • JupyterLab >= 3.0

Install

To install the extension, execute:

pip install papyri_lab

Uninstall

To remove the extension, execute:

pip uninstall papyri_lab

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 papyri_lab 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 papyri_lab
# 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 papyri_lab
pip uninstall papyri_lab

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 papyri-lab within that folder.

Packaging the extension

See RELEASE

Usage

For the time being you might need

  • this beanch of IPython.
  • To run papyri gen <some lib> and papyri ingest <some lib>

This will change in the future but is required for now.

How does this work.

  • when you do soemthing? in JupyterLab the IPython kernel will send a message to the frontend: {'papyri/help':'open doc for something'}

  • The JupyterLab extension will see this message and ask the Jupyterserver to

    • search in ~/.papyri/ingest/<yourlib>/<version>/<something>,
    • load the data,
    • send it back to JupyterLab
  • JupyterLab renders it in a side-pannel with plots and all.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published