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.
Fix: The sticky header on the HTML report didn't work unless you had branch
coverage enabled. This is now fixed: the sticky header works for everyone.
(Do people still use coverage without branch measurement!? j/k)
Fix: When using explicitly declared namespace packages, the "already imported
a file that will be measured" warning would be issued (issue 888_). This
is now fixed.
Deprecated: The annotate command and the Coverage.annotate function
will be removed in a future version, unless people let me know that they are
using it. Instead, the html command gives better-looking (and more
accurate) output, and the report -m command will tell you line numbers of
missing lines. Please get in touch if you have a reason to use annotate
over those better options: ned@nedbatchelder.com.
Feature: Coverage now sets an environment variable, COVERAGE_RUN when
running your code with the coverage run command. The value is not
important, and may change in the future. Closes issue 553_.
Feature: The HTML report pages for Python source files now have a sticky
header so the file name and controls are always visible.
Feature: The xml and json commands now describe what they wrote
where.
Feature: The html, combine, xml, and json commands all accept
a -q/--quiet option to suppress the messages they write to stdout about
what they are doing (issue 1254_).
Feature: The html command writes a .gitignore file into the HTML
output directory, to prevent the report from being committed to git. If you
want to commit it, you will need to delete that file. Closes issue 1244_.
Feature: Added support for PyPy 3.8.
Fix: More generated code is now excluded from measurement. Code such as
attrs_ boilerplate, or doctest code, was being measured though the
synthetic line numbers meant they were never reported. Once Cython was
involved though, the generated .so files were parsed as Python, raising
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.1.1.
Release notes
Sourced from coverage's releases.
Changelog
Sourced from coverage's changelog.
... (truncated)
Commits
ff59658
docs: sample HTML report for 6.1.17957d0a
build: prep for 6.1.14a772b5
perf(test): run pip just once, shaves 1.2s off the fixtureadff230
test: use the coverage-command fixture throughout the venv tests1a6844a
fix: don't warn about already imported files for namespace packages #8887589066
refactor(test): the virtualenv tests deserve their own file3b7f8c1
test: check pylint for new files before adding them to git56713f2
docs: another link for the no-jquery changelog entrybb78d7e
test: when we measure our coverage, get a json report also79f832f
build: clean up the Makefile a bitDependabot 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)