Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency coverage to v6 - autoclosed #42

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 10, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
coverage ==4.5.4 -> ==6.5.0 age adoption passing confidence
coverage ==5.3 -> ==6.5.0 age adoption passing confidence

Release Notes

nedbat/coveragepy

v6.5.0

Compare Source

  • The JSON report now includes details of which branches were taken, and which
    are missing for each file. Thanks, Christoph Blessing <pull 1438_>. Closes
    issue 1425
    .

  • Starting with coverage.py 6.2, class statements were marked as a branch.
    This wasn't right, and has been reverted, fixing issue 1449_. Note this
    will very slightly reduce your coverage total if you are measuring branch
    coverage.

  • Packaging is now compliant with PEP 517, closing issue 1395.

  • A new debug option --debug=pathmap shows details of the remapping of
    paths that happens during combine due to the [paths] setting.

  • Fix an internal problem with caching of invalid Python parsing. Found by
    OSS-Fuzz, fixing their bug 50381_.

.. _bug 50381: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381
.. _PEP 517: https://peps.python.org/pep-0517/
.. _issue 139https://github.com/nedbat/coveragepy/issues/1395395
.. _issue 14https://github.com/nedbat/coveragepy/issues/14251425
.. _issue 1https://github.com/nedbat/coveragepy/issues/1449/1449
.. _pull https://github.com/nedbat/coveragepy/pull/1438l/1438

.. _changes_6-4-4:

v6.4.4

Compare Source

  • Wheels are now provided for Python 3.11.

.. _changes_6-4-3:

v6.4.3

Compare Source

  • Fix a failure when combining data files if the file names contained glob-like
    patterns. Thanks, Michael Krebs and Benjamin Schubert <pull 1405_>_.

  • Fix a messaging failure when combining Windows data files on a different
    drive than the current directory, closing issue 1428. Thanks, Lorenzo Micò <pull 1430_>.

  • Fix path calculations when running in the root directory, as you might do in
    a Docker container. Thanks Arthur Rio <pull 1403_>_.

  • Filtering in the HTML report wouldn't work when reloading the index page.
    This is now fixed. Thanks, Marc Legendre <pull 1413_>_.

  • Fix a problem with Cython code measurement, closing issue 972. Thanks,
    Matus Valo <pull 1347_>
    .

.. _issue 972:https://github.com/nedbat/coveragepy/issues/9722
.. _issue 1428https://github.com/nedbat/coveragepy/issues/142828
.. _pull 134https://github.com/nedbat/coveragepy/pull/1347347
.. _pull 14https://github.com/nedbat/coveragepy/issues/14031403
.. _pull 1https://github.com/nedbat/coveragepy/issues/1405/1405
.. _pull https://github.com/nedbat/coveragepy/issues/1413s/1413
.. _pullhttps://github.com/nedbat/coveragepy/pull/1430ll/1430

.. _changes_6-4-2:

v6.4.2

Compare Source

  • Updated for a small change in Python 3.11.0 beta 4: modules now start with a
    line with line number 0, which is ignored. This line cannnot be executed, so
    coverage totals were thrown off. This line is now ignored by coverage.py,
    but this also means that truly empty modules (like __init__.py) have no
    lines in them, rather than one phantom line. Fixes issue 1419_.

  • Internal debugging data added to sys.modules is now an actual module, to
    avoid confusing code that examines everything in sys.modules. Thanks,
    Yilei Yang <pull 1399_>_.

.. _issue 1419:https://github.com/nedbat/coveragepy/issues/14199
.. _pull 1399https://github.com/nedbat/coveragepy/pull/139999

.. _changes_6-4-1:

v6.4.1

Compare Source

  • Greatly improved performance on PyPy, and other environments that need the
    pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick (pull 1381_ and pull 1388). Slightly improved performance when using the C
    trace function, as most environments do. Closes issue 1339
    .

  • The conditions for using tomllib from the standard library have been made
    more precise, so that 3.11 alphas will continue to work. Closes issue 1390_.

.. _issue 1339:https://github.com/nedbat/coveragepy/issues/13399
.. _pull 1381https://github.com/nedbat/coveragepy/pull/138181
.. _pull 138https://github.com/nedbat/coveragepy/pull/1388388
.. _issue 13https://github.com/nedbat/coveragepy/issues/13901390

.. _changes_64:

v6.4

Compare Source

  • Wheels are now provided for Python 3.11.

.. _changes_6-4-3:

v6.3.3

Compare Source

  • Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again.
    Closes issue 1367_. Some results for generators may have changed.

.. _issue 1367:https://github.com/nedbat/coveragepy/issues/13677

.. _changes_632:

v6.3.2

Compare Source

  • Fix: adapt to pypy3.9's decorator tracing behavior. It now traces function
    decorators like CPython 3.8: both the @​-line and the def-line are traced.
    Fixes issue 1326_.

  • Debug: added pybehave to the list of :ref:coverage debug <cmd_debug>
    and :ref:cmd_run_debug options.

  • Fix: show an intelligible error message if --concurrency=multiprocessing
    is used without a configuration file. Closes issue 1320_.

.. _issue 1320:https://github.com/nedbat/coveragepy/issues/13200
.. _issue 1326https://github.com/nedbat/coveragepy/issues/132626

.. _changes_631:

v6.3.1

Compare Source

  • Fix: deadlocks could occur when terminating processes. Some of these
    deadlocks (described in issue 1310_) are now fixed.

  • Fix: a signal handler was being set from multiple threads, causing an error:
    "ValueError: signal only works in main thread". This is now fixed, closing
    issue 1312_.

  • Fix: --precision on the command-line was being ignored while considering
    --fail-under. This is now fixed, thanks to
    Marcelo Trylesinski <pull 1317_>_.

  • Fix: releases no longer provide 3.11.0-alpha wheels. Coverage.py uses CPython
    internal fields which are moving during the alpha phase. Fixes issue 1316_.

.. _issue 1310:https://github.com/nedbat/coveragepy/issues/13100
.. _issue 1312https://github.com/nedbat/coveragepy/issues/131212
.. _issue 131https://github.com/nedbat/coveragepy/issues/1316316
.. _pull 13https://github.com/nedbat/coveragepy/pull/13171317

.. _changes_63:

v6.3

Compare Source

  • Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again.
    Closes issue 1367_. Some results for generators may have changed.

.. _issue 1367:https://github.com/nedbat/coveragepy/issues/13677

.. _changes_632:

v6.2

Compare Source

  • Feature: Now the --concurrency setting can now have a list of values, so
    that threads and another lightweight threading package can be measured
    together, such as --concurrency=gevent,thread. Closes issue 1012_ and
    issue 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 Django
    setting 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 with
    multiprocessing wouldn't suppress the data file suffix (issue 989_). This
    is now fixed.

  • Debug: The coverage debug data command will now sniff out combinable data
    files, and report on all of them.

  • Debug: The coverage debug command used to accept a number of topics at a
    time, 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 while
    combining, the [run] relative_files setting was ignored, resulting in
    absolute 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 read
    files (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_). Although
    I'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_). This
    is 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 while
    combining, the [run] relative_files setting was ignored, resulting in
    absolute 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 read
    files (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_). Although
    I'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 now
    fixed.

  • Packages named as "source packages" (with source, or source_pkgs, or
    pytest-cov's --cov) might have been only partially measured. Their
    top-level statements could be marked as unexecuted, because they were
    imported by coverage.py before measurement began (issue 1232_). This is
    now 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 return
    a 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

  • Changes to file pattern matching, which might require updating your
    configuration:

    • Previously, * would incorrectly match directory separators, making
      precise matching difficult. This is now fixed, closing issue 1407_.

    • Now ** matches any number of nested directories, including none.

  • Improvements to combining data files when using the
    :ref:config_run_relative_files setting:

    • During coverage combine, relative file paths are implicitly combined
      without needing a [paths] configuration setting. This also fixed
      issue 991_.

    • A [paths] setting like */foo will now match foo/bar.py so that
      relative file paths can be combined more easily.

    • The setting is properly interpreted in more places, fixing issue 1280_.

  • Fixed environment variable expansion in pyproject.toml files. It was overly
    broad, causing errors outside of coverage.py settings, as described in issue 1481_ and issue 1345_. This is now fixed, but in rare cases will require
    changing your pyproject.toml to quote non-string values that use environment
    substitution.

  • Fixed internal logic that prevented coverage.py from running on
    implementations other than CPython or PyPy (issue 1474_).

.. _issue 991:https://github.com/nedbat/coveragepy/issues/9911
.. _issue 1280https://github.com/nedbat/coveragepy/issues/128080
.. _issue 134https://github.com/nedbat/coveragepy/issues/1345345
.. _issue 14https://github.com/nedbat/coveragepy/issues/14071407
.. _issue 1https://github.com/nedbat/coveragepy/issues/1474/1474
.. _issue https://github.com/nedbat/coveragepy/issues/1481s/1481

.. _changes_6-5-0:

v5.5

Compare Source

  • coverage combine has a new option, --keep to keep the original data
    files after combining them. The default is still to delete the files after
    they have been combined. This was requested in issue 1108_ and implemented
    in pull request 1110_. Thanks, Éric Larivière.

  • When reporting missing branches in coverage report, branches aren't
    reported 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_ and issue 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 TOTAL
    line, 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 and skip_empty settings in the configuration file
    can now be specified in the [html] section, so that text reports and HTML
    reports 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 previous
    versions. This performance regression is now fixed, closing issue 1037_.

  • Mysterious SQLite errors can happen on PyPy, as reported in issue 1010_. An
    immediate 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 previous
    versions. This performance regression is now fixed, closing issue 1037_.

  • Mysterious SQLite errors can happen on PyPy, as reported in issue 1010_. An
    immediate 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).

v5.2

Compare Source

  • The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858 and pull request 931).
  • The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).
  • The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779 and pull request 932).
  • The --skip-empty option is now available for the XML report, closing issue 976.
  • The coverage report command now accepts a --sort option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).
  • If coverage fails due to the coverage total not reaching the --fail-under value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).
  • TOML configuration files with non-ASCII characters would cause errors on Windows (issue 990). This is now fixed.
  • The output of --debug=trace now includes information about how the --source option is being interpreted, and the module names being considered.

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, Kjell Braden.
  • The get_option() and set_option() methods can now manipulate the [paths] configuration setting. Thanks to Bernát Gábor for the fix for issue 967.

v5.0.4

Compare Source

  • If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. 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 and pull request 945). Thanks, Abdeali Kothari.

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. Huge thanks 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.

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 debug information 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, since their 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 now fixed (issue 907).

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 and issue 900. This is now fixed, thanks to David Szotten.
  • When using coverage run --concurrency=multiprocessing, all data files should 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.

v5.0

Compare Source

  • The JSON report now includes details of which branches were taken, and which
    are missing for each file. Thanks, Christoph Blessing <pull 1438_>. Closes
    issue 1425
    .

  • Starting with coverage.py 6.2, class statements were marked as a branch.
    This wasn't right, and has been reverted, fixing issue 1449_. Note this
    will very slightly reduce your coverage total if you are measuring branch
    coverage.

  • Packaging is now compliant with PEP 517, closing issue 1395.

  • A new debug option --debug=pathmap shows details of the remapping of
    paths that happens during combine due to the [paths] setting.

  • Fix an internal problem with caching of invalid Python parsing. Found by
    OSS-Fuzz, fixing their bug 50381_.

.. _bug 50381: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381
.. _PEP 517: https://peps.python.org/pep-0517/
.. _issue 139https://github.com/nedbat/coveragepy/issues/1395395
.. _issue 14https://github.com/nedbat/coveragepy/issues/14251425
.. _issue 1https://github.com/nedbat/coveragepy/issues/1449/1449
.. _pull https://github.com/nedbat/coveragepy/pull/1438l/1438

.. _changes_6-4-4:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@coveralls
Copy link

coveralls commented Nov 10, 2021

Pull Request Test Coverage Report for Build 3508102177

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 91.525%

Totals Coverage Status
Change from base Build 1611593859: 0.0%
Covered Lines: 162
Relevant Lines: 177

💛 - Coveralls

@renovate renovate bot changed the title Update dependency coverage to v6 Update dependency coverage to v6 - autoclosed Mar 16, 2023
@renovate renovate bot closed this Mar 16, 2023
@renovate renovate bot deleted the renovate/coverage-6.x branch March 16, 2023 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant