Update dependency coverage to v5 - autoclosed #17
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:
==4.4.2
->==5.5
Release Notes
nedbat/coveragepy
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
The dark mode HTML report still used light colors for the context listing,
making them unreadable (
issue 1009
_). This is now fixed.The time stamp on the HTML report now includes the time zone. Thanks, Xie
Yanbo (
pull request 960
_)... _pull request 960:https://github.com/nedbat/coveragepy/pull/9600
.. _issue 1009https://github.com/nedbat/coveragepy/issues/100909
.. _changes_52:
v5.2
Compare Source
The dark mode HTML report still used light colors for the context listing,
making them unreadable (
issue 1009
_). This is now fixed.The time stamp on the HTML report now includes the time zone. Thanks, Xie
Yanbo (
pull request 960
_)... _pull request 960:https://github.com/nedbat/coveragepy/pull/9600
.. _issue 1009https://github.com/nedbat/coveragepy/issues/100909
.. _changes_52:
v5.1
Compare Source
The JSON report now includes counts of covered and missing branches. Thanks,
Salvatore Zagaria.
On Python 3.8, try-finally-return reported wrong branch coverage with
decorated async functions (
issue 964
_). This is now fixed. Thanks, KjellBraden.
The :meth:
~coverage.Coverage.get_option
and:meth:
~coverage.Coverage.set_option
methods can now manipulate the[paths]
configuration setting. Thanks to Bernát Gábor for the fix forissue 967
_... _issue 964:https://github.com/nedbat/coveragepy/issues/9644
.. _issue 967https://github.com/nedbat/coveragepy/issues/96767
.. _changes_504:
v5.0.4
Compare Source
If using the
[run] relative_files
setting, the XML report will userelative files in the
<source>
elements indicating the location of sourcecode. Closes
issue 948
_.The textual summary report could report missing lines with negative line
numbers on PyPy3 7.1 (
issue 943
_). This is now fixed.Windows wheels for Python 3.8 were incorrectly built, but are now fixed.
(
issue 949
_)Updated Python 3.9 support to 3.9a4.
HTML reports couldn't be sorted if localStorage wasn't available. This is now
fixed: sorting works even though the sorting setting isn't retained. (
issue 944
_ andpull request 945
_). Thanks, Abdeali Kothari... _issue 943:https://github.com/nedbat/coveragepy/issues/9433
.. _issue 944https://github.com/nedbat/coveragepy/issues/94444
.. _pull request 94https://github.com/nedbat/coveragepy/pull/945945
.. _issue 9https://github.com/nedbat/coveragepy/issues/948/948
.. _issue https://github.com/nedbat/coveragepy/issues/949s/949
.. _changes_503:
v5.0.3
Compare Source
A performance improvement in 5.0.2 didn't work for test suites that changed
directory before combining data, causing "Couldn't use data file: no such
table: meta" errors (
issue 916
_). This is now fixed.Coverage could fail to run your program with some form of "ModuleNotFound" or
"ImportError" trying to import from the current directory. This would happen
if coverage had been packaged into a zip file (for example, on Windows), or
was found indirectly (for example, by pyenv-virtualenv). A number of
different scenarios were described in
issue 862
_ which is now fixed. Hugethanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and
George-Cristian Bîrzan for protracted debugging sessions.
Added the "premain" debug option.
Added SQLite compile-time options to the "debug sys" output.
.. _issue 862:https://github.com/nedbat/coveragepy/issues/8622
.. _issue 916https://github.com/nedbat/coveragepy/issues/91616
.. _changes_502:
v5.0.2
Compare Source
Programs that used multiprocessing and changed directories would fail under
coverage. This is now fixed (
issue 890
_). A side effect is that debuginformation about the config files read now shows absolute paths to the
files.
When running programs as modules (
coverage run -m
) with--source
,some measured modules were imported before coverage starts. This resulted in
unwanted warnings ("Already imported a file that will be measured") and a
reduction in coverage totals (
issue 909
_). This is now fixed.If no data was collected, an exception about "No data to report" could happen
instead of a 0% report being created (
issue 884
_). This is now fixed.The handling of source files with non-encodable file names has changed.
Previously, if a file name could not be encoded as UTF-8, an error occurred,
as described in
issue 891
_. Now, those files will not be measured, sincetheir data would not be recordable.
A new warning ("dynamic-conflict") is issued if two mechanisms are trying to
change the dynamic context. Closes
issue 901
_.coverage run --debug=sys
would fail with an AttributeError. This is nowfixed (
issue 907
_)... _issue 884:https://github.com/nedbat/coveragepy/issues/8844
.. _issue 890https://github.com/nedbat/coveragepy/issues/89090
.. _issue 89https://github.com/nedbat/coveragepy/issues/891891
.. _issue 9https://github.com/nedbat/coveragepy/issues/901/901
.. _issue https://github.com/nedbat/coveragepy/issues/907s/907
.. _issuehttps://github.com/nedbat/coveragepy/issues/909es/909
.. _changes_501:
v5.0.1
Compare Source
If a 4.x data file is the cause of a "file is not a database" error, then use
a more specific error message, "Looks like a coverage 4.x data file, are you
mixing versions of coverage?" Helps diagnose the problems described in
issue 886
_.Measurement contexts and relative file names didn't work together, as
reported in
issue 899
_ andissue 900
_. This is now fixed, thanks toDavid Szotten.
When using
coverage run --concurrency=multiprocessing
, all data filesshould be named with parallel-ready suffixes. 5.0 mistakenly named the main
process' file with no suffix when using
--append
. This is now fixed,closing
issue 880
_.Fixed a problem on Windows when the current directory is changed to a
different drive (
issue 895
_). Thanks, Olivier Grisel.Updated Python 3.9 support to 3.9a2.
.. _issue 880:https://github.com/nedbat/coveragepy/issues/8800
.. _issue 886https://github.com/nedbat/coveragepy/issues/88686
.. _issue 89https://github.com/nedbat/coveragepy/issues/895895
.. _issue 8https://github.com/nedbat/coveragepy/issues/899/899
.. _issue https://github.com/nedbat/coveragepy/issues/900s/900
.. _changes_50:
v5.0
Compare Source
If using the
[run] relative_files
setting, the XML report will userelative files in the
<source>
elements indicating the location of sourcecode. Closes
issue 948
_.The textual summary report could report missing lines with negative line
numbers on PyPy3 7.1 (
issue 943
_). This is now fixed.Windows wheels for Python 3.8 were incorrectly built, but are now fixed.
(
issue 949
_)Updated Python 3.9 support to 3.9a4.
HTML reports couldn't be sorted if localStorage wasn't available. This is now
fixed: sorting works even though the sorting setting isn't retained. (
issue 944
_ andpull request 945
_). Thanks, Abdeali Kothari... _issue 943:https://github.com/nedbat/coveragepy/issues/9433
.. _issue 944https://github.com/nedbat/coveragepy/issues/94444
.. _pull request 94https://github.com/nedbat/coveragepy/pull/945945
.. _issue 9https://github.com/nedbat/coveragepy/issues/948/948
.. _issue https://github.com/nedbat/coveragepy/issues/949s/949
.. _changes_503:
v4.5.4
Compare Source
issue 828
_... _issue 828:https://github.com/nedbat/coveragepy/issues/8288
.. _changes_453:
v4.5.3
Compare Source
.. _changes_452:
v4.5.2
Compare Source
Namespace packages are supported on Python 3.7, where they used to cause
TypeErrors about path being None. Fixes
issue 700
_.Python 3.8 (as of today!) passes all tests. Fixes
issue 707
_ andissue 714
_.Development moved from
Bitbucket
_ toGitHub
_... _issue 700:https://github.com/nedbat/coveragepy/issues/7000
.. _issue 707https://github.com/nedbat/coveragepy/issues/70707
.. _issue 71https://github.com/nedbat/coveragepy/issues/714714
.. _Bitbucket: https://bitbucket.org
.. _GitHub: https://github.com/nedbat/coveragepy
.. _changes_451:
v4.5.1
Compare Source
Now that 4.5 properly separated the
[run] omit
and[report] omit
settings, an old bug has become apparent. If you specified a package name
for
[run] source
, then omit patterns weren't matched inside that package.This bug (
issue 638
_) is now fixed.On Python 3.7, reporting about a decorated function with no body other than a
docstring would crash coverage.py with an IndexError (
issue 640
_). This isnow fixed.
Configurer plugins are now reported in the output of
--debug=sys
... _issue 638:https://github.com/nedbat/coveragepy/issues/6388
.. _issue 640https://github.com/nedbat/coveragepy/issues/64040
.. _changes_45:
v4.5
Compare Source
issue 828
_... _issue 828:https://github.com/nedbat/coveragepy/issues/8288
.. _changes_453:
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 WhiteSource Renovate. View repository job log here.