Metadata
Release files for tfex 0.0.6
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 | |
|---|---|---|---|---|
| tfex-0.0.6.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tfex-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.4 kB
Release files / tfex-0.0.6.tar.gz
| Download URL | tfex-0.0.6.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a30be45e364fe4d9e699400be1c4c3e0cd7ec121bcddff363dcc080eb25ada3
|
|
BLAKE2b-256 checksum How to use checksums |
a315c880383881bd0dc2824a21fc695b17b2e31959c9be5bd1ce645a81831b53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.37.0 CPython/3.7.4
|
Release files / tfex-0.0.6-py3-none-any.whl
| Download URL | tfex-0.0.6-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41eb560ba01761a88e35744b2852abd2a0d265bb6a1f77b61ef62557800f2b55
|
|
BLAKE2b-256 checksum How to use checksums |
8d55e7b4f636480763ceec95d4aafe5ad8b8aab7d567a8d906339485c3c6fdb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.37.0 CPython/3.7.4
|
Security for tfex 0.0.6
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.