Metadata
Release files for xtime 0.0.1
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 | |
|---|---|---|---|---|
| xtime-0.0.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xtime-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.7 kB
Release files / xtime-0.0.1.tar.gz
| Download URL | xtime-0.0.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bae8e6ecc00a68bdb0a943f13cc76e88eca6b295763fde8fe9af3f1d48afdc56
|
|
BLAKE2b-256 checksum How to use checksums |
475c34778be951e086cec2372384a52367185c11136b8aacec5ae67e835772d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Release files / xtime-0.0.1-py3-none-any.whl
| Download URL | xtime-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d84f6a8bd2a92cf189e6ee07f52f44821f1ef295db57bd5ea2ba070c30bb442
|
|
BLAKE2b-256 checksum How to use checksums |
53ac27f40db050c9e6ae55990cd915d43b93ff5c07384508a0bc4df70743010b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Security for xtime 0.0.1
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.