custom_onnx
A Custom Jupyter Widget Library
Installation
You can install using pip:
pip install custom_onnx
If you are using Jupyter Notebook 5.2 or earlier, you may also need to enable the nbextension:
jupyter nbextension enable --py [--sys-prefix|--user|--system] custom_onnx
Development Installation
Create a dev environment:
conda create -n custom_onnx-dev -c conda-forge nodejs yarn python jupyterlab
conda activate custom_onnx-dev
Install the python. This will also build the TS package.
pip install -e ".[test, examples]"
When developing your extensions, you need to manually enable your extensions with the notebook / lab frontend. For lab, this is done by the command:
jupyter labextension develop --overwrite .
yarn run build
For classic notebook, you need to run:
jupyter nbextension install --sys-prefix --symlink --overwrite --py custom_onnx
jupyter nbextension enable --sys-prefix --py custom_onnx
Note that the --symlink flag doesn't work on Windows, so you will here have to run
the install command every time that you rebuild your extension. For certain installations
you might also need another flag instead of --sys-prefix, but we won't cover the meaning
of those flags here.
How to see your changes
Typescript:
If you use JupyterLab to develop then 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 widget.
# Watch the source directory in one terminal, automatically rebuilding when needed
yarn run watch
# Run JupyterLab in another terminal
jupyter lab
After a change wait for the build to finish and then refresh your browser and the changes should take effect.
Python:
If you make a change to the python code then you will need to restart the notebook kernel to have it take effect.
Updating the version
To update the version, install tbump and use it to bump the version. By default it will also create a tag.
pip install tbump
tbump <new-version>
Metadata
Release files for custom-onnx 0.1.1
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 | Actions |
|---|---|---|---|---|
| custom_onnx-0.1.1.tar.gz | 33.4 MB | Without provenance | Details for custom_onnx-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| custom_onnx-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for custom_onnx-0.1.1-py3-none-any.whl |
Total release size: 53.6 MB
Release files / custom_onnx-0.1.1.tar.gz
| Download URL | custom_onnx-0.1.1.tar.gz |
|---|---|
| Size | 33.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6feb17ca4a227946956d7e9285b6583193673f4589e453f32a03dedc1ea5fa63
|
|
BLAKE2b-256 checksum How to use checksums |
dc02a6589502fc18e52db2b89178f7717b85cf694053313a1b1651faa770e0d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Release files / custom_onnx-0.1.1-py3-none-any.whl
| Download URL | custom_onnx-0.1.1-py3-none-any.whl |
|---|---|
| Size | 20.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24d38291ad49900b9d09f84b60295ff21f9d882b555e94e4d2e67b464c341c84
|
|
BLAKE2b-256 checksum How to use checksums |
9c0484ce7219b0230f868ffc11d09215558c1608d3569ebd580614c53601229c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for custom-onnx 0.1.1
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.