Metadata
Release files for python-aemet-forecast 0.0.1
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 | |
|---|---|---|---|---|
| python-aemet_forecast-0.0.1.tar.gz | 8.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_aemet_forecast-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.1 kB
Release files / python-aemet_forecast-0.0.1.tar.gz
| Download URL | python-aemet_forecast-0.0.1.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa004230f4dcff39471bbe33f7a8bb20bb7ccc491ef8b67a0549a6a49cd4d2bc
|
|
BLAKE2b-256 checksum How to use checksums |
089a3cbf001e86e5de3c889e5b871147a5fa546c38174b3f74de9246c447318c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Release files / python_aemet_forecast-0.0.1-py3-none-any.whl
| Download URL | python_aemet_forecast-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2da59c63ac2483f62c23f0cb25299f33612a6c9ca8db676b30e192d6dc37b22
|
|
BLAKE2b-256 checksum How to use checksums |
cd1e082bbe32a20431683fa751018fb60d175b8ecdcd4e10cf9fe8b07c843515
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Security for python-aemet-forecast 0.0.1
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.