Metadata
1 maintainer
Release files for uw-memcached-clients 1.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 | |
|---|---|---|---|---|
| uw_memcached_clients-1.1.2.tar.gz | 10.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_memcached_clients-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.2 kB
Release files / uw_memcached_clients-1.1.2.tar.gz
| Download URL | uw_memcached_clients-1.1.2.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
054386a29d88733db099bb1a7b01f636a7f258d70fc160864662d16115cff0b9
|
|
BLAKE2b-256 checksum How to use checksums |
3bd36679af50012f42e049adac1ff46a91f991980be49dcd2bbdc77ad9053062
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / uw_memcached_clients-1.1.2-py3-none-any.whl
| Download URL | uw_memcached_clients-1.1.2-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
588817de8d013c3601806209e9979c12f38c68f3a3cad173c2e3562ca76df70c
|
|
BLAKE2b-256 checksum How to use checksums |
86c6cb246ba0ea6ca5782f6d1d7810ade6aba362e7e3a161c0306e2ad821ad60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for uw-memcached-clients 1.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.
