Metadata
1 maintainer
Release files for UW-RestClients-GWS 2.3.9
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_restclients_gws-2.3.9.tar.gz | 19.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_gws-2.3.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.7 kB
Release files / uw_restclients_gws-2.3.9.tar.gz
| Download URL | uw_restclients_gws-2.3.9.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6a59e45a8320dd08b0d1b79250861a341e20cac8e677d191878ce818f2e27c9
|
|
BLAKE2b-256 checksum How to use checksums |
404efb51e2c766873fdf60cf8397748ed60401c8db92e901d6d6d13ef605b7f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / uw_restclients_gws-2.3.9-py3-none-any.whl
| Download URL | uw_restclients_gws-2.3.9-py3-none-any.whl |
|---|---|
| Size | 29.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0aff6eddc16df929f79dafab7ebe2629f9137a2f61b0487b9e10327d23ee65c4
|
|
BLAKE2b-256 checksum How to use checksums |
aa25a9854d5ea3b2208cede72a309ea2d4949690c337d6ab0af6d6837ee01e7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for UW-RestClients-GWS 2.3.9
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.
