Skip to main content

jupyterlab_nodeeditor

Github Actions StatusBinder 一个节点编辑器

Requirements

  • JupyterLab >= 3.0

Install

To install the extension, execute:

pip install jupyterlab_nodeeditor

Uninstall

To remove the extension, execute:

pip uninstall jupyterlab_nodeeditor

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_nodeeditor directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# 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

pip uninstall jupyterlab_nodeeditor

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

Packaging the extension

See RELEASE

Metadata

Release files for jupyterlab-nodeeditor 1.0.10

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jupyterlab-nodeeditor 1.0.10
File Size Uploaded Provenance
jupyterlab_nodeeditor-1.0.10.tar.gz 5.1 MB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for jupyterlab-nodeeditor 1.0.10
File Interpreter ABI Platform
jupyterlab_nodeeditor-1.0.10-py3-none-any.whl Python 3 none any Details

Total release size: 6.3 MB

Release files / jupyterlab_nodeeditor-1.0.10.tar.gz

Download URL jupyterlab_nodeeditor-1.0.10.tar.gz
Size 5.1 MB
Tags Source
SHA-256 checksum
How to use checksums
a39d246e7dd5ef61f181aa3a8a314f6752748cd53523201e45672959178e5f91
BLAKE2b-256 checksum
How to use checksums
df266c5f5c134cf5d222f54c490e3edb711902761c2ab9890bb4dd58e33cba7b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.8.18

Release files / jupyterlab_nodeeditor-1.0.10-py3-none-any.whl

Download URL jupyterlab_nodeeditor-1.0.10-py3-none-any.whl
Size 1.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
01610248ef69477c7ac17097e7de412c3bf36410b05edd94ae1ed65ca7bad17a
BLAKE2b-256 checksum
How to use checksums
2a63a8efa48954dd8c496907c1cc776cfb21a3cd794ef076fe0ffa6cdedfcd3e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.8.18

Security for jupyterlab-nodeeditor 1.0.10

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page