Third-party packages are now ignored in coverage reporting. This solves a few problems:
Coverage will no longer report about other people’s code (issue 876). This is true even when using --source=. with a venv in the current directory.
Coverage will no longer generate “Already imported a file that will be measured” warnings about coverage itself (issue 905).
The HTML report uses j/k to move up and down among the highlighted chunks of code. They used to highlight the current chunk, but 5.0 broke that behavior. Now the highlighting is working again.
The JSON report now includes percent_covered_display, a string with the total percentage, rounded to the same number of decimal places as the other reports’ totals.
The coverage html command now prints a message indicating where the HTML
report was written. Fixes issue 1195_.
The coverage combine command now prints messages indicating each data
file being combined. Fixes issue 1105_.
The HTML report now includes a sentence about skipped files due to
skip_covered or skip_empty settings. Fixes issue 1163_.
Unrecognized options in the configuration file are no longer errors. They are
now warnings, to ease the use of coverage across versions. Fixes issue 1035_.
Fix handling of exceptions through context managers in Python 3.10. A missing
exception is no longer considered a missing branch from the with statement.
Fixes issue 1205_.
Fix another rarer instance of "Error binding parameter 0 - probably
unsupported type." (issue 1010_).
Creating a directory for the coverage data file now is safer against
conflicts when two coverage runs happen simultaneously (pull 1220_).
Thanks, Clément Pit-Claudel.
Dropped support for Python 2.7, PyPy 2, and Python 3.5.
Added support for the Python 3.10 match/case syntax.
Data collection is now thread-safe. There may have been rare instances of
exceptions raised in multi-threaded programs.
Plugins (like the Django coverage plugin) were generating "Already
imported a file that will be measured" warnings about Django itself. These
have been fixed, closing issue 1150.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps coverage from 5.5 to 6.0.
Release notes
Sourced from coverage's releases.
Changelog
Sourced from coverage's changelog.
... (truncated)
Commits
9515c4d
docs: 6.0 sample HTML reporte179cf6
build: prep for 6.0 release5a99516
docs: update the link to shining panda4d61fff
test: fix flaky multiprocessing tests0ded3df
chore: update requirements5bcfc26
test: update pylint1677bbb
Python 3.10.0rc2626875f
docs: thanks, Clément Pit-Claudelf531212
fix: Avoid a race condition in misc.ensure_dir (#1220)c0a9811
test: another test suggested by Mark ShannonDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)