The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pytest-hy 0.1.0
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_hy-0.1.0.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_hy-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 kB
Release files / pytest_hy-0.1.0.tar.gz
| Download URL | pytest_hy-0.1.0.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a7b93fbf335733e22f85e04f8833441a72dc361cc80900d6868634b78deda29
|
|
BLAKE2b-256 checksum How to use checksums |
33e1d3353a15f6de6248e6dc116559be110a2fac0102700ae9629a558596699a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / pytest_hy-0.1.0-py3-none-any.whl
| Download URL | pytest_hy-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66f4df806be75f735dbc9bc0f9dfc0d6cf4479ae6415f23d32f2ece9a3b1a5f7
|
|
BLAKE2b-256 checksum How to use checksums |
aa6e6528ccc4f7a22ca4c1c1eea4bd8b4f0962a8d74e8ad53be17ef4b7c1a879
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for pytest-hy 0.1.0
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.
