Metadata
Release files for pkgexamplesubmodules 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 | |
|---|---|---|---|---|
| pkgexamplesubmodules-0.0.2.tar.gz | 2.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pkgexamplesubmodules-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / pkgexamplesubmodules-0.0.2.tar.gz
| Download URL | pkgexamplesubmodules-0.0.2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0a811e0f60e527e52771269db7381ce21bfeb81e2397b40f9f1131d27677375
|
|
BLAKE2b-256 checksum How to use checksums |
56c2c6d02eb6d687c335b473ef9a4dde9a709dfaa6148b76c8f5362d1fa8d6b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Release files / pkgexamplesubmodules-0.0.2-py3-none-any.whl
| Download URL | pkgexamplesubmodules-0.0.2-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3dc346f083f6d7c8b2fcbd6ac80f132dd4dd38a404bfd9543029a41c3cf53a5
|
|
BLAKE2b-256 checksum How to use checksums |
f467018b0372acbd8390b66df3355fe0a75788b1a527b68cf0c13bdc78929a81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for pkgexamplesubmodules 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.