Release files for pgctl 5.2.1
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 | |
|---|---|---|---|---|
| pgctl-5.2.1.tar.gz | 23.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pgctl-5.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.0 kB
Release files / pgctl-5.2.1.tar.gz
| Download URL | pgctl-5.2.1.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b008351f4ba556800df44f59c75126ba61d8364c482c669199c55a889e8cd87
|
|
BLAKE2b-256 checksum How to use checksums |
9038b6a442975c4fa9452edc4598ad3ab9f780b96773f4a35f0d7537a2e104a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.5.0.1 requests/2.26.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.7.5
|
Release files / pgctl-5.2.1-py3-none-any.whl
| Download URL | pgctl-5.2.1-py3-none-any.whl |
|---|---|
| Size | 30.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
495f85b47338bbecf47866b94eece82ba316ebd893dc8ef6a26d55fe980d3070
|
|
BLAKE2b-256 checksum How to use checksums |
64d84353ff3d624fbc8ee7aa413fb7a51ef3872b25f69ff1b8e146eb0aca43cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.5.0.1 requests/2.26.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.7.5
|
Security for pgctl 5.2.1
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.
