coverage_enable_subprocess
enable python coverage for subprocesses
Decision gist · record as of 2026-08-14
No. The package is abandoned (last release 2016, last commit 2018) with no indication of compatibility with modern Python or coverage versions. The problem it solves—subprocess coverage tracking—may now be better addressed by current coverage.py features or alternative approaches. Only install if you are locked to a legacy Python version and coverage version where this package is known to work.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires coverage to be installed; the .pth mechanism depends on Python's site-packages directory being writable and site.py being active.
- Installation is straightforward with no complex dependencies beyond coverage itself.
- However, the package is abandoned—last release was in 2016 and last commit in 2018—so it may not work reliably with modern Python or coverage versions.
License · maintenance · safety
MIT (permissive) — MIT license permits unrestricted use, modification, and distribution with minimal restrictions, making it safe for most projects.
last release 2016-05-11 (3747 days) · last repo commit 2018-07-08 · 11 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 223,678 downloads/mo, #9,242 on PyPI
Alternatives
Verify before relying
pip install coverage-enable-subprocess
export COVERAGE_PROCESS_START=$PWD/.coveragerc
python your_script.py
coverage report- Compatibility with current coverage.py versions and modern Python (3.8+) is unclear given the 2016 release date.
- Whether the .pth mechanism still works as intended on current Python installations and virtual environments.
What it is and what it does
This package solves the problem of measuring code coverage across subprocess boundaries in Python. When you run tests or applications that spawn child processes, coverage.py normally only tracks the parent process. This package installs a .pth file into your Python environment that activates coverage.py's process_startup feature automatically, enabling coverage collection in subprocesses without requiring explicit code changes.
The package is designed for test suites that spawn multiple processes in parallel or that change directories during execution. You configure it by setting the COVERAGE_PROCESS_START environment variable to point to a .coveragerc file, and then any Python process started in that environment will automatically have coverage tracking enabled. The package depends only on coverage being installed.
Use it for
- Measure code coverage in test suites that spawn worker processes or run tests in parallel.
- Track coverage across multiprocessing applications without modifying application code.
- Collect coverage data from subprocess calls in build or deployment scripts.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
No.
The package is abandoned (last release 2016, last commit 2018) with no indication of compatibility with modern Python or coverage versions. The problem it solves—subprocess coverage tracking—may now be better addressed by current coverage.py features or alternative approaches. Only install if you are locked to a legacy Python version and coverage version where this package is known to work.
Install
coverage-enable-subprocess on PyPI
Before you install
Installation is straightforward with no complex dependencies beyond coverage itself. However, the package is abandoned—last release was in 2016 and last commit in 2018—so it may not work reliably with modern Python or coverage versions.
Requires coverage to be installed; the .pth mechanism depends on Python's site-packages directory being writable and site.py being active.
License in practice
MIT license permits unrestricted use, modification, and distribution with minimal restrictions, making it safe for most projects.
Quickstart
pip install coverage-enable-subprocess
export COVERAGE_PROCESS_START=$PWD/.coveragerc
python your_script.py
coverage reportVerify before relying
- Compatibility with current coverage.py versions and modern Python (3.8+) is unclear given the 2016 release date.
- Whether the .pth mechanism still works as intended on current Python installations and virtual environments.
Package facts
| License | MIT permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagecoverage |
| Maintenance | Abandoned 3,747 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 223,678 / month, #9,242 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | License :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 2.6Programming Language :: Python :: 2.7Programming Language :: Python :: 3.3Programming Language :: Python :: 3.4 |
Evidence: coverage_enable_subprocess-1.0-py2.py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “coverage subprocess tracking”
- coverage_enable_subprocessInstalls a .pth file that automatically enables coverage.py's…
- pytest-covA pytest plugin that measures code coverage during test runs,…
- pytest-shutilProvides pytest fixtures and utilities for managing temporary…
Give your agent the search over MCP, or paste the wish link into any chat.
More Quality Assurance packages
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
Ruff is a Python linter and code formatter written in Rust that combines linting, formatting, and code fixing into a single tool, replacing Flake8, Black, isort, and related utilities.
Pexpect spawns and controls interactive console applications by sending input and matching output patterns, automating tasks that would otherwise require manual interaction.
Black reformats Python source code to a consistent style by parsing entire files and rewriting them according to an opinionated, deterministic set of rules, eliminating manual formatting decisions.
pytest-xdist distributes pytest tests across multiple CPU cores or machines to speed up test execution, with the simplest usage being `pytest -n auto` to spawn workers equal to available CPUs.
Install it if your test suite takes long enough that parallelization would save meaningful time.
Validates AWS CloudFormation templates in YAML or JSON format against resource provider schemas and best practices, checking property values and configuration correctness.
Install it if you work with CloudFormation templates.
See also django-coverage-plugin · covdefaults · pytest-cover · coverage-conditional-plugin · pytest-forked · pytest-cov · cov-core · mutmut · python-coveralls