📙 Run jupyter lab in an LSF host and map its port. Learn more in GitHub!
1 maintainer
Metadata
1 maintainer
Release files for jupyterlab-lsf 0.1.2
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 | |
|---|---|---|---|---|
| jupyterlab-lsf-0.1.2.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyterlab_lsf-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.9 kB
Release files / jupyterlab-lsf-0.1.2.tar.gz
| Download URL | jupyterlab-lsf-0.1.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
235e07b55c93d4c797645d9d04926f71b64aff6799da42a73dcd9bf524afec35
|
|
BLAKE2b-256 checksum How to use checksums |
ea0313b1ff8c92db86cc52f06d401419c2e401143e7ea7062efca32d68cc7687
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / jupyterlab_lsf-0.1.2-py3-none-any.whl
| Download URL | jupyterlab_lsf-0.1.2-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b5a0ff8f53804aef4892f40019c1ffa79395a51aa67deb0079c8871a106ae42
|
|
BLAKE2b-256 checksum How to use checksums |
b5f9a96b9e3740c09dc2b4729e545991ddfcbe53e5e4ab5c66ca0ebd3a12cb1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for jupyterlab-lsf 0.1.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.
