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 contains the following updates:
>=5.1
->>=6.2
Release Notes
nedbat/coveragepy
v6.2
Compare Source
Feature: Now the
--concurrency
setting can now have a list of values, sothat threads and another lightweight threading package can be measured
together, such as
--concurrency=gevent,thread
. Closesissue 1012
_ andissue 1082
_.Fix: A module specified as the
source
setting is imported during startup,before the user program imports it. This could cause problems if the rest of
the program isn't ready yet. For example,
issue 1203
_ describes a Djangosetting that is accessed before settings have been configured. Now the early
import is wrapped in a try/except so errors then don't stop execution.
Fix: A colon in a decorator expression would cause an exclusion to end too
early, preventing the exclusion of the decorated function. This is now fixed.
Fix: The HTML report now will not overwrite a .gitignore file that already
exists in the HTML output directory (follow-on for
issue 1244
_).API: The exceptions raised by Coverage.py have been specialized, to provide
finer-grained catching of exceptions by third-party code.
API: Using
suffix=False
when constructing a Coverage object withmultiprocessing wouldn't suppress the data file suffix (
issue 989
_). Thisis now fixed.
Debug: The
coverage debug data
command will now sniff out combinable datafiles, and report on all of them.
Debug: The
coverage debug
command used to accept a number of topics at atime, and show all of them, though this was never documented. This no longer
works, to allow for command-line options in the future.
.. _issue 989:https://github.com/nedbat/coveragepy/issues/9899
.. _issue 1012https://github.com/nedbat/coveragepy/issues/101212
.. _issue 108https://github.com/nedbat/coveragepy/issues/1082082
.. _issue 12https://github.com/nedbat/coveragepy/issues/12031203
.. _changes_612:
v6.1.2
Compare Source
Python 3.11 is supported (tested with 3.11.0a2). One still-open issue has to
do with
exits through with-statements <issue 1270_>
_.Fix: When remapping file paths through the
[paths]
setting whilecombining, the
[run] relative_files
setting was ignored, resulting inabsolute paths for remapped file names (
issue 1147
_). This is now fixed.Fix: Complex conditionals over excluded lines could have incorrectly reported
a missing branch (
issue 1271
_). This is now fixed.Fix: More exceptions are now handled when trying to parse source files for
reporting. Problems that used to terminate coverage.py can now be handled
with
[report] ignore_errors
. This helps with plugins failing to readfiles (
django_coverage_plugin issue 78
_).Fix: Removed another vestige of jQuery from the source tarball
(
issue 840
_).Fix: Added a default value for a new-to-6.x argument of an internal class.
This unsupported class is being used by coveralls (
issue 1273
_). AlthoughI'd rather not "fix" unsupported interfaces, it's actually nicer with a
default value.
.. _django_coverage_plugin issue 78:https://github.com/nedbat/django_coverage_plugin/issues/788
.. _issue 1147https://github.com/nedbat/coveragepy/issues/114747
.. _issue 127https://github.com/nedbat/coveragepy/issues/1270270
.. _issue 12https://github.com/nedbat/coveragepy/issues/12711271
.. _issue 1https://github.com/nedbat/coveragepy/issues/1273/1273
.. _changes_611:
v6.1.1
Compare Source
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
_). Thisis now fixed.
.. _issue 888:https://github.com/nedbat/coveragepy/issues/8888
.. _changes_61:
v6.1
Compare Source
Python 3.11 is supported (tested with 3.11.0a2). One still-open issue has to
do with
exits through with-statements <issue 1270_>
_.Fix: When remapping file paths through the
[paths]
setting whilecombining, the
[run] relative_files
setting was ignored, resulting inabsolute paths for remapped file names (
issue 1147
_). This is now fixed.Fix: Complex conditionals over excluded lines could have incorrectly reported
a missing branch (
issue 1271
_). This is now fixed.Fix: More exceptions are now handled when trying to parse source files for
reporting. Problems that used to terminate coverage.py can now be handled
with
[report] ignore_errors
. This helps with plugins failing to readfiles (
django_coverage_plugin issue 78
_).Fix: Removed another vestige of jQuery from the source tarball
(
issue 840
_).Fix: Added a default value for a new-to-6.x argument of an internal class.
This unsupported class is being used by coveralls (
issue 1273
_). AlthoughI'd rather not "fix" unsupported interfaces, it's actually nicer with a
default value.
.. _django_coverage_plugin issue 78:https://github.com/nedbat/django_coverage_plugin/issues/788
.. _issue 1147https://github.com/nedbat/coveragepy/issues/114747
.. _issue 127https://github.com/nedbat/coveragepy/issues/1270270
.. _issue 12https://github.com/nedbat/coveragepy/issues/12711271
.. _issue 1https://github.com/nedbat/coveragepy/issues/1273/1273
.. _changes_611:
v6.0.2
Compare Source
Namespace packages being measured weren't properly handled by the new code
that ignores third-party packages. If the namespace package was installed, it
was ignored as a third-party package. That problem (
issue 1231
_) is nowfixed.
Packages named as "source packages" (with
source
, orsource_pkgs
, orpytest-cov's
--cov
) might have been only partially measured. Theirtop-level statements could be marked as unexecuted, because they were
imported by coverage.py before measurement began (
issue 1232
_). This isnow fixed, but the package will be imported twice, once by coverage.py, then
again by your test suite. This could cause problems if importing the package
has side effects.
The :meth:
.CoverageData.contexts_by_lineno
method was documented to returna dict, but was returning a defaultdict. Now it returns a plain dict. It
also no longer returns negative numbered keys.
.. _issue 1231:https://github.com/nedbat/coveragepy/issues/12311
.. _issue 1232https://github.com/nedbat/coveragepy/issues/123232
.. _changes_601:
v6.0.1
Compare Source
In 6.0, the coverage.py exceptions moved from coverage.misc to
coverage.exceptions. These exceptions are not part of the public supported
API, CoverageException is. But a number of other third-party packages were
importing the exceptions from coverage.misc, so they are now available from
there again (
issue 1226
_).Changed an internal detail of how tomli is imported, so that tomli can use
coverage.py for their own test suite (
issue 1228
_).Defend against an obscure possibility under code obfuscation, where a
function can have an argument called "self", but no local named "self"
(
pull request 1210
_). Thanks, Ben Carlsson... _pull request 1210:https://github.com/nedbat/coveragepy/pull/12100
.. _issue 1226https://github.com/nedbat/coveragepy/issues/122626
.. _issue 122https://github.com/nedbat/coveragepy/issues/1228228
.. _changes_60:
v6.0
Compare Source
Namespace packages being measured weren't properly handled by the new code
that ignores third-party packages. If the namespace package was installed, it
was ignored as a third-party package. That problem (
issue 1231
_) is nowfixed.
Packages named as "source packages" (with
source
, orsource_pkgs
, orpytest-cov's
--cov
) might have been only partially measured. Theirtop-level statements could be marked as unexecuted, because they were
imported by coverage.py before measurement began (
issue 1232
_). This isnow fixed, but the package will be imported twice, once by coverage.py, then
again by your test suite. This could cause problems if importing the package
has side effects.
The :meth:
.CoverageData.contexts_by_lineno
method was documented to returna dict, but was returning a defaultdict. Now it returns a plain dict. It
also no longer returns negative numbered keys.
.. _issue 1231:https://github.com/nedbat/coveragepy/issues/12311
.. _issue 1232https://github.com/nedbat/coveragepy/issues/123232
.. _changes_601:
v5.5
Compare Source
coverage combine
has a new option,--keep
to keep the original datafiles after combining them. The default is still to delete the files after
they have been combined. This was requested in
issue 1108
_ and implementedin
pull request 1110
_. Thanks, Éric Larivière.When reporting missing branches in
coverage report
, branches aren'treported that jump to missing lines. This adds to the long-standing behavior
of not reporting branches from missing lines. Now branches are only reported
if both the source and destination lines are executed. Closes both
issue 1065
_ andissue 955
_.Minor improvements to the HTML report:
The state of the line visibility selector buttons is saved in local storage
so you don't have to fiddle with them so often, fixing
issue 1123
_.It has a little more room for line numbers so that 4-digit numbers work
well, fixing
issue 1124
_.Improved the error message when combining line and branch data, so that users
will be more likely to understand what's happening, closing
issue 803
_... _issue 803:https://github.com/nedbat/coveragepy/issues/8033
.. _issue 955https://github.com/nedbat/coveragepy/issues/95555
.. _issue 106https://github.com/nedbat/coveragepy/issues/1065065
.. _issue 11https://github.com/nedbat/coveragepy/issues/11081108
.. _pull request 1https://github.com/nedbat/coveragepy/pull/1110/1110
.. _issue https://github.com/nedbat/coveragepy/issues/1123s/1123
.. _issuehttps://github.com/nedbat/coveragepy/issues/1124es/1124
.. _changes_54:
v5.4
Compare Source
The text report produced by
coverage report
now always outputs a TOTALline, even if only one Python file is reported. This makes regex parsing
of the output easier. Thanks, Judson Neer. This had been requested a number
of times (
issue 1086
,issue 922
,issue 732
_).The
skip_covered
andskip_empty
settings in the configuration filecan now be specified in the
[html]
section, so that text reports and HTMLreports can use separate settings. The HTML report will still use the
[report]
settings if there isn't a value in the[html]
section.Closes
issue 1090
_.Combining files on Windows across drives now works properly, fixing
issue 577
. Thanks,Valentin Lab <pr1080_>
.Fix an obscure warning from deep in the decimal module, as reported in
issue 1084
.Update to support Python 3.10 alphas in progress, including
PEP 626: Precise line numbers for debugging and other tools <pep626_>
_... _issue 577:https://github.com/nedbat/coveragepy/issues/5777
.. _issue 732https://github.com/nedbat/coveragepy/issues/73232
.. _issue 92https://github.com/nedbat/coveragepy/issues/922922
.. _issue 10https://github.com/nedbat/coveragepy/issues/10841084
.. _issue 1https://github.com/nedbat/coveragepy/issues/1086/1086
.. _issue https://github.com/nedbat/coveragepy/issues/1090s/1090
.. _phttps://github.com/nedbat/coveragepy/pull/1080ll/1080
.. _pep626: https://www.python.org/dev/peps/pep-0626/
.. _changes_531:
v5.3.1
Compare Source
When using
--source
on a large source tree, v5.x was slower than previousversions. This performance regression is now fixed, closing
issue 1037
_.Mysterious SQLite errors can happen on PyPy, as reported in
issue 1010
_. Animmediate retry seems to fix the problem, although it is an unsatisfying
solution.
The HTML report now saves the sort order in a more widely supported way,
fixing
issue 986
. Thanks, Sebastián Ramírez (pull request 1066
).The HTML report pages now have a :ref:
Sleepy Snake <sleepy>
favicon.Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).
Continuous integration has moved from Travis and AppVeyor to GitHub Actions.
.. _issue 986:https://github.com/nedbat/coveragepy/issues/9866
.. _issue 1037https://github.com/nedbat/coveragepy/issues/103737
.. _issue 101https://github.com/nedbat/coveragepy/issues/1010010
.. _pull request 10https://github.com/nedbat/coveragepy/pull/10661066
.. _changes_53:
v5.3
Compare Source
When using
--source
on a large source tree, v5.x was slower than previousversions. This performance regression is now fixed, closing
issue 1037
_.Mysterious SQLite errors can happen on PyPy, as reported in
issue 1010
_. Animmediate retry seems to fix the problem, although it is an unsatisfying
solution.
The HTML report now saves the sort order in a more widely supported way,
fixing
issue 986
. Thanks, Sebastián Ramírez (pull request 1066
).The HTML report pages now have a :ref:
Sleepy Snake <sleepy>
favicon.Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).
Continuous integration has moved from Travis and AppVeyor to GitHub Actions.
.. _issue 986:https://github.com/nedbat/coveragepy/issues/9866
.. _issue 1037https://github.com/nedbat/coveragepy/issues/103737
.. _issue 101https://github.com/nedbat/coveragepy/issues/1010010
.. _pull request 10https://github.com/nedbat/coveragepy/pull/10661066
.. _changes_53:
v5.2.1
Compare Source
v5.2
Compare Source
coverage report
andcoverage html
commands now accept a--precision
option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).coverage report
andcoverage html
commands now accept a--no-skip-covered
option to negate--skip-covered
. Thanks, Anthony Sottile (issue 779 and pull request 932).--skip-empty
option is now available for the XML report, closing issue 976.coverage report
command now accepts a--sort
option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).--fail-under
value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).--debug=trace
now includes information about how the--source
option is being interpreted, and the module names being considered.Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.