Release files for pytest-pop 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 | |
|---|---|---|---|---|
| pytest-pop-1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_pop-1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.6 kB
Release files / pytest-pop-1.tar.gz
| Download URL | pytest-pop-1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
543348a905b80a5879fe97914bf49415b7795e5c4ea5b95f681d781ec2e6f8cc
|
|
BLAKE2b-256 checksum How to use checksums |
aa78f4db96fecd1fa5b769e0065463a44dda33fde36006c5c8a1a9d9849d35e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Release files / pytest_pop-1-py3-none-any.whl
| Download URL | pytest_pop-1-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd445e2e450a12114235e8676c3577624b4219f63056f1ec88b383e47cd11134
|
|
BLAKE2b-256 checksum How to use checksums |
7dfb56fab71f04ca7c3c7c8ac27e7f85d7bda9dfd92591c8aaf5f8392d1c253d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Security for pytest-pop 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.
