1 maintainer
Metadata
1 maintainer
Release files for pycq 0.4.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 | |
|---|---|---|---|---|
| pycq-0.4.2.tar.gz | 8.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pycq-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.9 kB
Release files / pycq-0.4.2.tar.gz
| Download URL | pycq-0.4.2.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e3b5ef98d36b69ace048b1cc375904dbbf97e741fcf035729146deb3a5297c0
|
|
BLAKE2b-256 checksum How to use checksums |
5d05d13ce4ccc6eb0b1a3541ce72c8a81cccc733e38f73e95cff7311e5a85cba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.21.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.3
|
Release files / pycq-0.4.2-py3-none-any.whl
| Download URL | pycq-0.4.2-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d15dabeba886cc0414df840fb39424e2f994ea8ebfd4e9b7e319ab28a258ae8
|
|
BLAKE2b-256 checksum How to use checksums |
218cef22a31a4702de0b62f39cc9d421b6d2faf72c30550f2ff97691ff214331
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.21.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.3
|
Security for pycq 0.4.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.
