mlworkbench
TigerGraph ML Workbench
Requirements
- JupyterLab >= 3.0
Install
To install the extension, execute:
pip install tigergraph_mlworkbench
Uninstall
To remove the extension, execute:
pip uninstall tigergraph_mlworkbench
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 mlworkbench 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 run 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 run 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 run 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 tigergraph_mlworkbench
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 mlworkbench within that folder.
Packaging the extension
See RELEASE
1 maintainer
Metadata
1 maintainer
Release files for tigergraph-mlworkbench 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tigergraph_mlworkbench-1.0.0.tar.gz | 151.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tigergraph_mlworkbench-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 202.9 kB
Release files / tigergraph_mlworkbench-1.0.0.tar.gz
| Download URL | tigergraph_mlworkbench-1.0.0.tar.gz |
|---|---|
| Size | 151.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
973340e334794b02cf9e8c3b77003f1e491c24c966e2215f565b946db743d98d
|
|
BLAKE2b-256 checksum How to use checksums |
953d058f111b3b35cb1d709ee924abd0546ba785a33d260e06e2cf05c00c92ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Release files / tigergraph_mlworkbench-1.0.0-py3-none-any.whl
| Download URL | tigergraph_mlworkbench-1.0.0-py3-none-any.whl |
|---|---|
| Size | 51.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ceac67a0d66d841988eb60dd9e2f2efc147ef57bcbb922ee57aea87a72023fe
|
|
BLAKE2b-256 checksum How to use checksums |
12913747dca72b26a1055f7a704618369b8838f1f6828bebfad74d7884b9005a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Security for tigergraph-mlworkbench 1.0.0
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.
