Repository navigation
Fix coverage collection for empty --cov values - #768
Merged
Merged
Conversation
ionelmc
force-pushed
the
fix-empty-cov-source
branch
from
October 18, 2026 16:54
a81fc4f to
8823b4f
Compare
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.
Passing
--cov=leaves an empty source name, so coverage collects no files even when.coveragercsetssource.Normalize the empty value to the existing bare
--covbehavior and update the configuration example.Validation: all six new regression cases fail before the fix and pass afterward. On Windows with Python 3.13.13, the full suite had 209 passed, 6 skipped, and 1 pre-existing duplicate-plugin registration failure. Changed-file pre-commit checks, strict Sphinx build, and package checks passed. The full pre-commit run hit a Taplo schema retrieval timeout; the documentation link check did not pass because of existing broken links and GitHub rate limits.