The author of this package has not provided a project description
Metadata
Release files for geedatasets 0.2.4
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 | |
|---|---|---|---|---|
| geedatasets-0.2.4.tar.gz | 31.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| geedatasets-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.0 kB
Release files / geedatasets-0.2.4.tar.gz
| Download URL | geedatasets-0.2.4.tar.gz |
|---|---|
| Size | 31.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
faef44b57ad2faa79333fa9dcc6c81972efd909d92a173962d21b7dc2d8c51a5
|
|
BLAKE2b-256 checksum How to use checksums |
0e1c39562e05d99e6a8ca66639cf6bde9dffa7a889f6933801e28abd2ed40710
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.8.19
|
Release files / geedatasets-0.2.4-py3-none-any.whl
| Download URL | geedatasets-0.2.4-py3-none-any.whl |
|---|---|
| Size | 34.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
363a427b533f381f437c150ddfc7d9c2598120e4289cca3442bd1f7007446c7a
|
|
BLAKE2b-256 checksum How to use checksums |
f007d2b8b50aa743a6e2178f4317bd641314fef6e7b9f67d6f6557838590f6f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.8.19
|
Security for geedatasets 0.2.4
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.