Release files for tricle 1.8
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 | |
|---|---|---|---|---|
| tricle-1.8.tar.gz | 10.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tricle-1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.7 kB
Release files / tricle-1.8.tar.gz
| Download URL | tricle-1.8.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d89ab407ef569779a3af1f3510bc728aa157e6cbddea69b44e233296f0f8f9ed
|
|
BLAKE2b-256 checksum How to use checksums |
416f3fdbba2651b46e702b6b4233f522a9983f9dc19fa433583e0d4f7e0adcd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.3
|
Release files / tricle-1.8-py3-none-any.whl
| Download URL | tricle-1.8-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3ccb1f7c5fa75dd981778af10d5d723b13bea570b7aaa744ac096dcccbe6a3a
|
|
BLAKE2b-256 checksum How to use checksums |
a2dfcc04855b065b14343d2811a3c76f22eb5f4549a08e12c5a07077aa2e8e2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.3
|
Security for tricle 1.8
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.
