Release files for anemoi-datasets 0.5.47
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 | |
|---|---|---|---|---|
| anemoi_datasets-0.5.47.tar.gz | 2.1 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| anemoi_datasets-0.5.47-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 MB
Release files / anemoi_datasets-0.5.47.tar.gz
| Download URL | anemoi_datasets-0.5.47.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e0e0892b4aa7c26fc06415b7b73cbeb27b7ff848d0aef3d32a2981247b45d23
|
|
BLAKE2b-256 checksum How to use checksums |
88f73cc7e2e0095f0844f94b432060014ea9befdcbd590a61fd8a344fa1aec63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.1
|
Release files / anemoi_datasets-0.5.47-py3-none-any.whl
| Download URL | anemoi_datasets-0.5.47-py3-none-any.whl |
|---|---|
| Size | 496.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e399635732bf4aeeaa6bf12ad70c3746e1c69d26e117b75ce4df4bc235997881
|
|
BLAKE2b-256 checksum How to use checksums |
627a8afad1a8556142c2be808e14037184517b026fa12a752d4ba1be76620da4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.1
|
Security for anemoi-datasets 0.5.47
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.
