Metadata
Release files for pkgexampleargparse 0.0.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 | |
|---|---|---|---|---|
| pkgexampleargparse-0.0.2.tar.gz | 3.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pkgexampleargparse-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.8 kB
Release files / pkgexampleargparse-0.0.2.tar.gz
| Download URL | pkgexampleargparse-0.0.2.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4372f2c9328173fe3f40790cd21ab858efd3d77e7e86a3fde1080091d663cdd3
|
|
BLAKE2b-256 checksum How to use checksums |
17318ceb237f967eb0afe215628a2b4956503adf7f07f9ccc6d3d705f855027e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Release files / pkgexampleargparse-0.0.2-py3-none-any.whl
| Download URL | pkgexampleargparse-0.0.2-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a06576a7128fc360ecc2a92fb8fe5f6e5d5769e0da819d8943b0488d738c9e32
|
|
BLAKE2b-256 checksum How to use checksums |
5ea3b8b63580cd9eebdf760c04d51573dce9c4f64e078fbf847797d72b72adea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Security for pkgexampleargparse 0.0.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.