Metadata
Release files for pyaerocom-parallelization 0.0.5
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 | |
|---|---|---|---|---|
| pyaerocom_parallelization-0.0.5.tar.gz | 24.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyaerocom_parallelization-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.2 kB
Release files / pyaerocom_parallelization-0.0.5.tar.gz
| Download URL | pyaerocom_parallelization-0.0.5.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7795980e7011b366114f2b5b751b6bce7b9dd3179b37255e7adc00dc8081466
|
|
BLAKE2b-256 checksum How to use checksums |
37d80ad8a3bb597a49c99fa21f710e66ded6184d1f3c11613337db6d102fd6cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Release files / pyaerocom_parallelization-0.0.5-py3-none-any.whl
| Download URL | pyaerocom_parallelization-0.0.5-py3-none-any.whl |
|---|---|
| Size | 24.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44079ac1cefd911b7ffba5c988998ed6015a58d0bfe505205c466c2a8a37384f
|
|
BLAKE2b-256 checksum How to use checksums |
b3a80c3bcdaf6d49fef84ae0a95a552c50f495e3b03040b4f84ec27bce1e626f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for pyaerocom-parallelization 0.0.5
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.