The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for TracGoogleStaticMapMacro 1.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 | |
|---|---|---|---|---|
| TracGoogleStaticMapMacro-1.1.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| TracGoogleStaticMapMacro-1.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 8.0 kB
Release files / TracGoogleStaticMapMacro-1.1.tar.gz
| Download URL | TracGoogleStaticMapMacro-1.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1042d59783d58d6d5c2394aa34114ca454462b05b7148fb593664d590cb6aad2
|
|
BLAKE2b-256 checksum How to use checksums |
a90843ed5ece503fd80133f05cb0417d21bc06e80b1de3c397c31160e6eb8186
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / TracGoogleStaticMapMacro-1.1-py2-none-any.whl
| Download URL | TracGoogleStaticMapMacro-1.1-py2-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
1205339617396cf55c5f7f1ce27203ef93b089015406464b9a9eb6e29f13a9ca
|
|
BLAKE2b-256 checksum How to use checksums |
8e8ee307a78b9d7b496cf2c586202e94d7baddabfb29be7185fc618bbebe19f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TracGoogleStaticMapMacro 1.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.
