{{ message }}
Allow excluding region reporting in all report types that support it#2135
Open
astei wants to merge 1 commit into
Open
Allow excluding region reporting in all report types that support it#2135astei wants to merge 1 commit into
astei wants to merge 1 commit into
Conversation
devdanzin
reviewed
Feb 18, 2026
Contributor
There was a problem hiding this comment.
This seems unrelated to your goals, does it become necessary due to the other changes?
Author
There was a problem hiding this comment.
Yes, the tests did not pass because of float representation being inexact, despite not changing the code that was being covered.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new flag,
--omit-regions, to the JSON and HTML reports.I use coverage.py on a particularly large monolithic application (several millions of lines of code), and we have custom tooling that parses JSON reports created by coverage.py. When region-level reporting was added to JSON reports, this tooling had a notable regression in memory usage and performance. We don't use this information, so it's helpful if coverage.py doesn't emit it in the first place.