Provides a pure Python parser for LCOV trace files.
Metadata
Release files for lcovparser 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 | |
|---|---|---|---|---|
| lcovparser-0.0.1.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lcovparser-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.9 kB
Release files / lcovparser-0.0.1.tar.gz
| Download URL | lcovparser-0.0.1.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8b2945e0686e1bb7cddd714977e2626fb630df9184d612e0d2e7543fc8b072e
|
|
BLAKE2b-256 checksum How to use checksums |
055b3b3d4bc225182738cb9e5100a65cb29b0b4a9d451293185c7cd1709c5b88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.12.2 Darwin/23.4.0
|
Release files / lcovparser-0.0.1-py3-none-any.whl
| Download URL | lcovparser-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ee79803e52a1c06b0f641e59ec52ed8865c4c3a7cab1d6affb71dccab79ddd2
|
|
BLAKE2b-256 checksum How to use checksums |
b9350a46002b8deacbb56251a5d47e3b10e9252255b55338b253445bfe429ef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.12.2 Darwin/23.4.0
|
Security for lcovparser 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.