coveragepy / coveragepy/coveragepy
Support gevent & thread concurrency in the same project
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.4k
- Forks
- 525
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
Please see the Readme on the repo to reproduce https://github.com/ddorian/coverage-bug-gevent. It shows an example where you are using gevent for all async, except those that are cpu-heavy which you use native threads.
Describe the solution you'd like
Ability to track both gevent & native threads.
Describe alternatives you've considered
Drop gevent and use async (too much work and dev-quality sucks) or only threads (high overhead).
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
Start with the README in the linked ddorian/coverage-bug-gevent repository and reproduce its mixed gevent and native-thread example. Trace how coverage.py handles these two concurrency modes, then verify that coverage is collected from both gevent-based work and native threads without dropping either.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100