coveragepy / coveragepy/django_coverage_plugin
Using this package with sysmon
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 202
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Since Python 3.14 will now allow me to use sys.monitoring for branch coverage, the last obstacle (for me!) remains this package.
I've found a decent workaround: marking every test that renders a template that I want to get coverage on and then running those without the environment variable, separately from the others, and combining the coverage files from the two test runs. Given the timings from my experimentation, this seems well worth the effort.
So this is really just a question: is there anything that can be done in this package or in Coverage.py (or I suppose, in my project) that can work around this in a more general way, without me needing to make this somewhat painstaking change to my codebase?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the separate template-rendering and non-template test runs with Python 3.14's sys.monitoring, then inspect the plugin and Coverage.py integration points involved in the environment variable and combined coverage files. Done means template coverage works generally without marking tests or maintaining separate runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100