🪐 🌳 Jupyter Environments
Environmnents for Jupyter.
Jupyter Environments allow Users to define the packages and libraries (Python...) that are used in their Kernels.
An Environment is also the place where Users define their Secrets and Environment Variables.
Develop
pip install -e .[test]
jupyter labextension develop . --overwrite
jupyter labextension list
jupyter server extension list
yarn jupyterlab
Metadata
Release files for jupyter-environments 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyter_environments-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for jupyter_environments-0.0.2-py3-none-any.whl |
Release files / jupyter_environments-0.0.2-py3-none-any.whl
| Download URL | jupyter_environments-0.0.2-py3-none-any.whl |
|---|---|
| Size | 12.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21e843058080969bda262caaad13bff9cc6fa3d648e2d0339ca5d2d33b326a22
|
|
BLAKE2b-256 checksum How to use checksums |
bac4c3c22ddd559c9a75c2a17514d7d038739a2180ae7a75d74c20feb803bd4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.13
|
Security for jupyter-environments 0.0.2
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.