Release files for pit 0.5
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 | |
|---|---|---|---|---|
| pit-0.5.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pit-0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.4 kB
Release files / pit-0.5.tar.gz
| Download URL | pit-0.5.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
404d5bdee676ccff0d403610f279249eea0c66a7b68cd906aa29fe79e00ec64f
|
|
BLAKE2b-256 checksum How to use checksums |
04c9c2566d0f304f10355f2d86735378a5d91ea3958f4521f000d553411d30a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.20.1 setuptools/40.5.0 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.0
|
Release files / pit-0.5-py3-none-any.whl
| Download URL | pit-0.5-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e02f625afd03465e11167021aa12e870e687861c9b88a23706631aa81c3f5802
|
|
BLAKE2b-256 checksum How to use checksums |
174005be603539e9075f236378c617e1c4f225d98945a86aa6388b078d09cf84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.20.1 setuptools/40.5.0 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.0
|
Security for pit 0.5
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.
