The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for awakeQuant 0.1.0
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 | |
|---|---|---|---|---|
| awakequant-0.1.0.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awakequant-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.4 kB
Release files / awakequant-0.1.0.tar.gz
| Download URL | awakequant-0.1.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7ed80e1f65728ef479b543716f67bb3c79485711d8552efe2c55b1802a5629e
|
|
BLAKE2b-256 checksum How to use checksums |
d14b67468428010481c8ab5bc01af63d41e4330b00dad3f8766eafba43125765
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.0
|
Release files / awakequant-0.1.0-py3-none-any.whl
| Download URL | awakequant-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1ffce6ab265b5b1db5c0cdb328c3ec8e34a46217a2669876111efb0987338e1
|
|
BLAKE2b-256 checksum How to use checksums |
cfcf2bd5888b13665961cb284a5feb395f9f1a06d23c04e5e553d431b065ba55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.0
|
Security for awakeQuant 0.1.0
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.
