This is a pytest report plugin
Based on Vue + element UI development, generate HTML file Very pretty ! Let’s try now
Metadata
Release files for pytest-tmreport 1.3.2
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-tmreport-1.3.2.tar.gz | 7.0 kB | Without provenance | Details |
Release files / pytest-tmreport-1.3.2.tar.gz
| Download URL | pytest-tmreport-1.3.2.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06154bba27674baa2ab587fca3b7dab8395c13c6339a1ba2516f733ab81bfd72
|
|
BLAKE2b-256 checksum How to use checksums |
0be4598c65c1d57c68d0de1667b84166733f19f11bb83136d30df5f9c13aed77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.8.2
|
Security for pytest-tmreport 1.3.2
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.