ipannotoryous
An annotation Jupyter Widget based on Annotorius.
Installation
You can install using pip:
pip install ipannotoryous
Or if you use JupyterLab 3:
pip install ipannotoryous
Or if you use JupyterLab 2:
pip install ipannotoryous
jupyter labextension install @jupyter-widgets/jupyterlab-manager ipannotoryous
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] ipannotoryous
Development Installation
# First install the python package. This will also build the JS packages.
pip install -e ".[test, examples]"
When developing your extensions, you need to manually enable your extensions with the notebook / lab frontend. For JupyterLab 3, this is done by the command:
jupyter labextension develop . --overwrite
For classic notebook, you can run:
jupyter nbextension install --sys-prefix --symlink --overwrite --py ipannotoryous
jupyter nbextension enable --sys-prefix --py ipannotoryous
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:
To continuously monitor the project for changes and automatically trigger a rebuild, start Jupyter in watch mode:
jupyter lab --watch
And in a separate session, begin watching the source directory for changes:
npm run watch
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.
Metadata
Release files for ipannotoryous 1.0.0.post1
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 |
|---|---|---|---|---|
| ipannotoryous-1.0.0.post1.tar.gz | 1.1 MB | Without provenance | Details for ipannotoryous-1.0.0.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ipannotoryous-1.0.0.post1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for ipannotoryous-1.0.0.post1-py2.py3-none-any.whl |
Total release size: 2.1 MB
Release files / ipannotoryous-1.0.0.post1.tar.gz
| Download URL | ipannotoryous-1.0.0.post1.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc82b6c7da587f5e7876da455ceaceaba3006957a25442e5f2a5bd3419a3f8e5
|
|
BLAKE2b-256 checksum How to use checksums |
e2589609bfc6031ccd11e13a17df66ae861a2d8a018ef7a253df93e44cb7f387
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/52.0.0.post20210125 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.9.1
|
Release files / ipannotoryous-1.0.0.post1-py2.py3-none-any.whl
| Download URL | ipannotoryous-1.0.0.post1-py2.py3-none-any.whl |
|---|---|
| Size | 978.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
572243c7a61b41bf39649e61faada25b510c6c7fbc019f54e22898194417a30e
|
|
BLAKE2b-256 checksum How to use checksums |
5ea53246b14925cdd8463c0db4854f562c24e9c551b3e942c82df00d5ea7f1e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/52.0.0.post20210125 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.9.1
|
Security for ipannotoryous 1.0.0.post1
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.