Release files for pytispark 2.0
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 | |
|---|---|---|---|---|
| pytispark-2.0.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytispark-2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / pytispark-2.0.tar.gz
| Download URL | pytispark-2.0.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6bf0153a8fb6c824c1aeb2b8456c4a6e7002242c6af4951be1746536faebb62
|
|
BLAKE2b-256 checksum How to use checksums |
ef485bab80f59d19fb0c7e7720cebe2324aa496fbc23668f7d98927e3cc2bd6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Release files / pytispark-2.0-py3-none-any.whl
| Download URL | pytispark-2.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2aaf3b9b840a74b74e08c14b2adec9170b670081fca7eeb9bf8201317e683d04
|
|
BLAKE2b-256 checksum How to use checksums |
d2c5b09c69ddc6dab157347cd6fb9577d856a89c814ede0ccd38080b3bf9509d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Security for pytispark 2.0
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.
