Metadata
4 maintainers
Release files for streamsx.geospatial 1.1.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 | |
|---|---|---|---|---|
| streamsx.geospatial-1.1.4.tar.gz | 11.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| streamsx.geospatial-1.1.4-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 24.3 kB
Release files / streamsx.geospatial-1.1.4.tar.gz
| Download URL | streamsx.geospatial-1.1.4.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8159412a1090e390617d2109f4d698491aad6eefe6c956a4657de5e38df90c3d
|
|
BLAKE2b-256 checksum How to use checksums |
56131e5bae6806c9de89e4b0c8fad4bd4e9c310ceb922468eb9ac7db7d8655d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Release files / streamsx.geospatial-1.1.4-py2.py3-none-any.whl
| Download URL | streamsx.geospatial-1.1.4-py2.py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c5529a33e5d88f0f72a8f1babff2a58c645d51bc64c2163b8605481efe1fd779
|
|
BLAKE2b-256 checksum How to use checksums |
a6677ed1c0ba8e279c2804ca136bf6394aa1c209af3a52fb66459c8f688c76d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for streamsx.geospatial 1.1.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.
