I wasn't accurate in a previous issue: this feature is also gating for my project.

In real-world programs, there are significant quantities of code within otherwise tested files which are deliberately not unit tested due to diminishing returns and finite resources.

coverage uses the exclude_lines configuration file setting to match lines and scopes not to be included in coverage, usually with a specific comment - docs.

This is informative when reading code, and it also gives a more useful measure of actual coverage.

This sounds harder than my previous issues, because of the fact it applies to scopes as well as single lines.

coverage has a ton of other features, several of which we do use, but IMHO these two are the most important.

Thanks again for a very promising library!