OBSOLETE - see opencivicdata package
4 maintainers
Metadata
4 maintainers
Release files for opencivicdata-divisions 3000
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 | |
|---|---|---|---|---|
| opencivicdata-divisions-3000.tar.gz | 879 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opencivicdata_divisions-3000-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 2.9 kB
Release files / opencivicdata-divisions-3000.tar.gz
| Download URL | opencivicdata-divisions-3000.tar.gz |
|---|---|
| Size | 879 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89840598d0b821612b1ed48f5819b83025ba474c70a009eb109ed6bc8d734dc8
|
|
BLAKE2b-256 checksum How to use checksums |
87de42ac7cbbb924a7f3f4f05e52098a30f488c15f9b5333bd5ae014e50a871a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / opencivicdata_divisions-3000-py2-none-any.whl
| Download URL | opencivicdata_divisions-3000-py2-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
dfb235684360b37821e421aff3610ac2f503753f7806c22bd759b82f9d774324
|
|
BLAKE2b-256 checksum How to use checksums |
c2575375c663901ac936f2ad78c4f51d23182c55e964b387d9fd7cd66d5ad0b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for opencivicdata-divisions 3000
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.
