meteogram
Create a meteogram based on data from met.no.
Documentation is available on Read the Docs.
Examples:
1 maintainer
Metadata
1 maintainer
Release files for meteogram 0.1.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 | |
|---|---|---|---|---|
| meteogram-0.1.2.tar.gz | 2.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meteogram-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.5 MB
Release files / meteogram-0.1.2.tar.gz
| Download URL | meteogram-0.1.2.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09d6043016a0e71474aa70d0bc1d747b99fc743f78e2de48b4644efc38ebfe49
|
|
BLAKE2b-256 checksum How to use checksums |
a0cbd034cadad2751e1a24c7e993a2a82f5041c98b5c9b40341c081d4a233afc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.3
|
Release files / meteogram-0.1.2-py3-none-any.whl
| Download URL | meteogram-0.1.2-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4869422e4f542b5da33512f06cec4be6822d794ef3195d15bbd372fcb066587
|
|
BLAKE2b-256 checksum How to use checksums |
e7284ae0cff797d98b9f8356e412949d4dc8ccb43692724ea2f180bd6cd1ef26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.3
|
Security for meteogram 0.1.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.
