The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for Plot1Qbit 0.23
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 | |
|---|---|---|---|---|
| Plot1Qbit-0.23.tar.gz | 7.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Plot1Qbit-0.23-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / Plot1Qbit-0.23.tar.gz
| Download URL | Plot1Qbit-0.23.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1019c5d09f519942a0955bca7b15e17f1e6743cba91f7741291569e04704530
|
|
BLAKE2b-256 checksum How to use checksums |
2047c0cecbf1eb73a444e8f1e2fba0622f95124dc6b422e15166085f8fa5bc9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Release files / Plot1Qbit-0.23-py3-none-any.whl
| Download URL | Plot1Qbit-0.23-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f442df0f8e43f7e4c9aa69904fc3bdf5327b10265c12863630f055ec5b8dccd
|
|
BLAKE2b-256 checksum How to use checksums |
1aeb18c816b623f1b38523716ff194ad9d27bf47c407e3c1466557905b76c65d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Security for Plot1Qbit 0.23
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.
