This package contains a .pth file that calls coverage.process_startup().
Usage
Install it with Pip:
$ pip install coverage-p
Then run your tests like:
$ COVERAGE_PROCESS_START="$PWD/.coveragerc" coverage run -p -m unittest ...
Each Python processes your tests spawn will generate a .coverage file. Merge these by running coverage combine.
See the Coverage.py document Measuring sub-processes for more information.
Why not coverage_pth?
The coverage_pth package attempts to do the same thing, but the wheels it provides only work on Python 3.6. It also appears unmaintained.
Compatiblity Policy
Any version of CPython supported upstream and by Coverage.py is considered supported and should be tested in CI. Additionally, CI covers supported 3.x releases of PyPy, subject to availability in GitHub Actions.
coverage-p is tested against the current version of Coverage.py. The API coverage-p invokes has been stable for many years, so compatibility issues are not expected.
Changelog
v25.2.0 (2025-02-01)
Add License-Expression metadata
Repackage with Hatchling
v24.7.0 (2024-07-06)
Initial release
Contributing
File issues and PRs on GitHub. See CONTRIBUTING.rst for more. Please follow the Twisted code of conduct.
License
coverage-p is made available under the MIT license.
1 maintainer
Metadata
1 maintainer
Release files for coverage-p 25.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| coverage_p-25.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Release files / coverage_p-25.2.0-py2.py3-none-any.whl
| Download URL | coverage_p-25.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
251f25ba55c4ec4eff77edef25ad35962be45d5af762cd0de6c3b0f43ca6bafa
|
|
BLAKE2b-256 checksum How to use checksums |
a2ac29b742b9420234311b221d050327ae56fdffb153cf164f9b56da95e64d5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 1, 2025.
Transparency log
