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 v7.6.9 #93

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 26, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
coverage 7.4.0 -> 7.6.9 age adoption passing confidence

Release Notes

nedbat/coveragepy (coverage)

v7.6.9

Compare Source

  • Fix: Tomas Uribe fixed <pull 1901_>_ a performance problem in the XML
    report. Large code bases should produce XML reports much faster now.

.. _pull 1901:https://github.com/nedbat/coveragepy/pull/19011

.. _changes_7-6-8:

v7.6.8

Compare Source

  • Fix: the LCOV report code assumed that a branch line that took no branches
    meant that the entire line was unexecuted. This isn't true in a few cases:
    the line might always raise an exception, or might have been optimized away.
    Fixes issue 1896_.

  • Fix: similarly, the HTML report will now explain that a line that jumps to
    none of its expected destinations must have always raised an exception.
    Previously, it would say something nonsensical like, "line 4 didn't jump to
    line 5 because line 4 was never true, and it didn't jump to line 7 because
    line 4 was always true." This was also shown in issue 1896_.

.. _issue 1896:https://github.com/nedbat/coveragepy/issues/18966

.. _changes_7-6-7:

v7.6.7

Compare Source

  • fix: ugh, the other assert from 7.6.5 can also be encountered in the wild,
    so it's been restored to a conditional. Sorry for the churn.

.. _changes_7-6-6:

v7.6.6

Compare Source

  • One of the new asserts from 7.6.5 caused problems in real projects, as
    reported in issue 1891_. The assert has been removed.

.. _issue 1891:https://github.com/nedbat/coveragepy/issues/18911

.. _changes_7-6-5:

v7.6.5

Compare Source

  • fix: fine-tuned the exact Python version (3.12.6) when exiting from with
    statements changed how they traced. This affected whether people saw the
    fix for issue 1880_.

  • fix: isolate our code more from mocking in the os module that in rare cases
    can cause bizarre behavior <pytest-cov-666_>_.

  • refactor: some code unreachable code paths in parser.py were changed to
    asserts. If you encounter any of these, please let me know!

.. _pytest-cov-666:https://github.com/pytest-dev/pytest-cov/issues/6666

.. _changes_7-6-4:

v7.6.4

Compare Source

  • fix: multi-line with statements could cause contained branches to be
    incorrectly marked as missing (issue 1880_). This is now fixed.

.. _issue 1880:https://github.com/nedbat/coveragepy/issues/18800

.. _changes_7-6-3:

v7.6.3

Compare Source

  • Fix: nested context managers could incorrectly be analyzed to flag a missing
    branch on the last context manager, as described in issue 1876_. This is
    now fixed.

  • Fix: the missing branch message about not exiting a module had an extra
    "didn't," as described in issue 1873_. This is now fixed.

.. _issue 1873:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676

.. _changes_7-6-2:

v7.6.2

Compare Source

  • Dropped support for Python 3.8 and PyPy 3.8.

  • Fix: a final wildcard match/case clause assigning to a name (case _ as value) was incorrectly marked as a missing branch. This is now fixed,
    closing issue 1860_.

  • Fewer things are considered branches now. Lambdas, comprehensions, and
    generator expressions are no longer marked as missing branches if they don't
    complete execution. Closes issue 1852_.

  • Fix: the HTML report didn't properly show multi-line f-strings that end with
    a backslash continuation. This is now fixed, closing issue 1836, thanks
    to LiuYinCarl and Marco Ricci <pull 1838_>
    .

  • Fix: the LCOV report now has correct line numbers (fixing issue 1846) and
    better branch descriptions for BRDA records (fixing issue 1850
    ). There
    are other changes to lcov also, including a new configuration option
    :ref:line_checksums <config_lcov_line_checksums> to control whether line
    checksums are included in the lcov report. The default is false. To keep
    checksums set it to true. All this work is thanks to Zack Weinberg
    (pull 1849_ and pull 1851_).

  • Fixed the docs for multi-line regex exclusions, closing issue 1863_.

  • Fixed a potential crash in the C tracer, closing issue 1835, thanks to
    Jan Kühle <pull 1843_>
    .

.. _issue 1835:https://github.com/nedbat/coveragepy/issues/18355
.. _issue 1836https://github.com/nedbat/coveragepy/issues/183636
.. _pull 183https://github.com/nedbat/coveragepy/pull/1838838
.. _pull 18https://github.com/nedbat/coveragepy/pull/18431843
.. _issue 1https://github.com/nedbat/coveragepy/issues/1846/1846
.. _pull https://github.com/nedbat/coveragepy/pull/1849l/1849
.. _issuehttps://github.com/nedbat/coveragepy/issues/1850es/1850
.. _pulhttps://github.com/nedbat/coveragepy/pull/1851ull/1851
.. _isshttps://github.com/nedbat/coveragepy/issues/1852sues/1852
.. _ishttps://github.com/nedbat/coveragepy/issues/1860ssues/1860
.. _ihttps://github.com/nedbat/coveragepy/issues/1863issues/1863

.. _changes_7-6-1:

v7.6.1

Compare Source

  • Fix: coverage used to fail when measuring code using :func:runpy.run_path <python:runpy.run_path> with a :class:Path <python:pathlib.Path> argument.
    This is now fixed, thanks to Ask Hjorth Larsen <pull 1819_>_.

  • Fix: backslashes preceding a multi-line backslashed string could confuse the
    HTML report. This is now fixed, thanks to LiuYinCarl <pull 1828_>_.

  • Now we publish wheels for Python 3.13, both regular and free-threaded.

.. _pull 1819:https://github.com/nedbat/coveragepy/pull/18199
.. _pull 1828https://github.com/nedbat/coveragepy/pull/182828

.. _changes_7-6-0:

v7.6.0

Compare Source

  • Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those
    requested in issues 118 <issue 118_>
    (entire files), 996 <issue 996_>_ (multiple lines only when appearing together), 1741 <issue 1741_>_ (remainder of a function), and 1803 <issue 1803_>_
    (arbitrary sequence of marked lines). See the :ref:multi_line_exclude
    section of the docs for more details and examples.

  • The JSON report now includes per-function and per-class coverage information.
    Thanks to Daniel Diniz <pull 1809_>_ for getting the work started. This
    closes issue 1793_ and issue 1532_.

  • Fixed an incorrect calculation of "(no class)" lines in the HTML classes
    report.

  • Python 3.13.0b3 is supported.

.. _issue 118:https://github.com/nedbat/coveragepy/issues/1188
.. _issue 996https://github.com/nedbat/coveragepy/issues/99696
.. _issue 153https://github.com/nedbat/coveragepy/issues/1532532
.. _issue 17https://github.com/nedbat/coveragepy/issues/17411741
.. _issue 1https://github.com/nedbat/coveragepy/issues/1793/1793
.. _issue https://github.com/nedbat/coveragepy/issues/1803s/1803
.. _pullhttps://github.com/nedbat/coveragepy/pull/1807ll/1807
.. _pulhttps://github.com/nedbat/coveragepy/pull/1809ull/1809

.. _changes_7-5-4:

v7.5.4

Compare Source

  • If you attempt to combine statement coverage data with branch coverage data,
    coverage.py used to fail with the message "Can't combine arc data with line
    data" or its reverse, "Can't combine line data with arc data." These
    messages used internal terminology, making it hard for people to understand
    the problem. They are now changed to mention "branch coverage data" and
    "statement coverage data."

  • Fixed a minor branch coverage problem with wildcard match/case cases using
    names or guard clauses.

  • Started testing on 3.13 free-threading (nogil) builds of Python. I'm not
    claiming full support yet. Closes issue 1799_.

.. _issue 1799:https://github.com/nedbat/coveragepy/issues/17999

.. _changes_7-5-3:

v7.5.3

Compare Source

  • Performance improvements for combining data files, especially when measuring
    line coverage. A few different quadratic behaviors were eliminated. In one
    extreme case of combining 700+ data files, the time dropped from more than
    three hours to seven minutes. Thanks for Kraken Tech for funding the fix.

  • Performance improvements for generating HTML reports, with a side benefit of
    reducing memory use, closing issue 1791_. Thanks to Daniel Diniz for
    helping to diagnose the problem.

.. _issue 1791:https://github.com/nedbat/coveragepy/issues/17911

.. _changes_7-5-2:

v7.5.2

Compare Source

  • Fix: nested matches of exclude patterns could exclude too much code, as
    reported in issue 1779_. This is now fixed.

  • Changed: previously, coverage.py would consider a module docstring to be an
    executable statement if it appeared after line 1 in the file, but not
    executable if it was the first line. Now module docstrings are never counted
    as executable statements. This can change coverage.py's count of the number
    of statements in a file, which can slightly change the coverage percentage
    reported.

  • In the HTML report, the filter term and "hide covered" checkbox settings are
    remembered between viewings, thanks to Daniel Diniz <pull 1776_>_.

  • Python 3.13.0b1 is supported.

  • Fix: parsing error handling is improved to ensure bizarre source files are
    handled gracefully, and to unblock oss-fuzz fuzzing, thanks to Liam DeVoe <pull 1788_>. Closes issue 1787.

.. _pull 1776:https://github.com/nedbat/coveragepy/pull/17766
.. _issue 1779https://github.com/nedbat/coveragepy/issues/177979
.. _issue 178https://github.com/nedbat/coveragepy/issues/1787787
.. _pull 17https://github.com/nedbat/coveragepy/pull/17881788

.. _changes_7-5-1:

v7.5.1

Compare Source

  • Fix: a pragma comment on the continuation lines of a multi-line statement
    now excludes the statement and its body, the same as if the pragma is
    on the first line. This closes issue 754. The fix was contributed by
    Daniel Diniz <pull 1773_>
    .

  • Fix: very complex source files like this one <resolvent_lookup_>_ could
    cause a maximum recursion error when creating an HTML report. This is now
    fixed, closing issue 1774_.

  • HTML report improvements:

    • Support files (JavaScript and CSS) referenced by the HTML report now have
      hashes added to their names to ensure updated files are used instead of
      stale cached copies.

    • Missing branch coverage explanations that said "the condition was never
      false" now read "the condition was always true" because it's easier to
      understand.

    • Column sort order is remembered better as you move between the index pages,
      fixing issue 1766. Thanks, Daniel Diniz <pull 1768_>.

.. _resolvent_lookup: https://github.com/sympy/sympy/blob/130950f3e6b3f97fcc17f4599ac08f70fdd2e9d4/sympy/polys/numberfields/resolvent_lookup.py
.. _issue 754https://github.com/nedbat/coveragepy/issues/75454
.. _issue 176https://github.com/nedbat/coveragepy/issues/1766766
.. _pull 17https://github.com/nedbat/coveragepy/pull/17681768
.. _pull 1https://github.com/nedbat/coveragepy/pull/1773/1773
.. _issue https://github.com/nedbat/coveragepy/issues/1774s/1774

.. _changes_7-5-0:

v7.5.0

Compare Source

  • Added initial support for function and class reporting in the HTML report.
    There are now three index pages which link to each other: files, functions,
    and classes. Other reports don't yet have this information, but it will be
    added in the future where it makes sense. Feedback gladly accepted!
    Finishes issue 780_.

  • Other HTML report improvements:

    • There is now a "hide covered" checkbox to filter out 100% files, finishing
      issue 1384_.

    • The index page is always sorted by one of its columns, with clearer
      indications of the sorting.

    • The "previous file" shortcut key didn't work on the index page, but now it
      does, fixing issue 1765_.

  • The debug output showing which configuration files were tried now shows
    absolute paths to help diagnose problems where settings aren't taking effect,
    and is renamed from "attempted_config_files" to the more logical
    "config_files_attempted."

  • Python 3.13.0a6 is supported.

.. _issue 780:https://github.com/nedbat/coveragepy/issues/7800
.. _issue 1384https://github.com/nedbat/coveragepy/issues/138484
.. _issue 176https://github.com/nedbat/coveragepy/issues/1765765

.. _changes_7-4-4:

v7.4.4

Compare Source

  • Fix: in some cases, even with [run] relative_files=True, a data file
    could be created with absolute path names. When combined with other relative
    data files, it was random whether the absolute file names would be made
    relative or not. If they weren't, then a file would be listed twice in
    reports, as detailed in issue 1752_. This is now fixed: absolute file
    names are always made relative when combining. Thanks to Bruno Rodrigues dos
    Santos for support.

  • Fix: the last case of a match/case statement had an incorrect message if the
    branch was missed. It said the pattern never matched, when actually the
    branch is missed if the last case always matched.

  • Fix: clicking a line number in the HTML report now positions more accurately.

  • Fix: the report:format setting was defined as a boolean, but should be a
    string. Thanks, Tanaydin Sirin <pull 1754_>_. It is also now documented
    on the :ref:configuration page <config_report_format>.

.. _issue 1752:https://github.com/nedbat/coveragepy/issues/17522
.. _pull 1754https://github.com/nedbat/coveragepy/pull/175454

.. _changes_7-4-3:

v7.4.3

Compare Source

  • Fix: in some cases, coverage could fail with a RuntimeError: "Set changed
    size during iteration." This is now fixed, closing issue 1733_.

.. _issue 1733:https://github.com/nedbat/coveragepy/issues/17333

.. _changes_7-4-2:

v7.4.2

Compare Source

  • Fix: setting COVERAGE_CORE=sysmon no longer errors on 3.11 and lower,
    thanks Hugo van Kemenade <pull 1747_>_. It now issues a warning that
    sys.monitoring is not available and falls back to the default core instead.

.. _pull 1747:https://github.com/nedbat/coveragepy/pull/17477

.. _changes_7-4-1:

v7.4.1

Compare Source

  • Python 3.13.0a3 is supported.

  • Fix: the JSON report now includes an explicit format version number, closing
    issue 1732_.

.. _issue 1732:https://github.com/nedbat/coveragepy/issues/17322

.. _changes_7-4-0:


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 this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from ee2c1fb to edd2345 Compare February 20, 2024 22:04
@renovate renovate bot changed the title Update dependency coverage to v7.4.1 Update dependency coverage to v7.4.2 Feb 20, 2024
@renovate renovate bot changed the title Update dependency coverage to v7.4.2 Update dependency coverage to v7.4.3 Feb 23, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from edd2345 to dfcb91b Compare February 23, 2024 22:26
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from dfcb91b to e3b38bf Compare March 14, 2024 20:00
@renovate renovate bot changed the title Update dependency coverage to v7.4.3 Update dependency coverage to v7.4.4 Mar 14, 2024
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@renovate renovate bot changed the title Update dependency coverage to v7.4.4 Update dependency coverage to v7.5.0 Apr 23, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from e3b38bf to 84b549d Compare April 23, 2024 19:07
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 84b549d to 272f818 Compare May 4, 2024 16:21
@renovate renovate bot changed the title Update dependency coverage to v7.5.0 Update dependency coverage to v7.5.1 May 4, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 272f818 to 05c641d Compare May 26, 2024 12:20
@renovate renovate bot changed the title Update dependency coverage to v7.5.1 Update dependency coverage to v7.5.2 May 26, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 05c641d to fe0137d Compare May 28, 2024 16:30
@renovate renovate bot changed the title Update dependency coverage to v7.5.2 Update dependency coverage to v7.5.3 May 28, 2024
@renovate renovate bot changed the title Update dependency coverage to v7.5.3 Update dependency coverage to v7.5.4 Jun 22, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from fe0137d to 1a2478f Compare June 22, 2024 22:35
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 1a2478f to 375c1fe Compare July 11, 2024 17:44
@renovate renovate bot changed the title Update dependency coverage to v7.5.4 Update dependency coverage to v7.6.0 Jul 11, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 375c1fe to 8469e8e Compare August 4, 2024 21:54
@renovate renovate bot changed the title Update dependency coverage to v7.6.0 Update dependency coverage to v7.6.1 Aug 4, 2024
Copy link

sonarqubecloud bot commented Aug 4, 2024

@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 8469e8e to 762b8d7 Compare October 9, 2024 13:39
@renovate renovate bot changed the title Update dependency coverage to v7.6.1 Update dependency coverage to v7.6.2 Oct 9, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 762b8d7 to 8bc095a Compare October 13, 2024 23:02
@renovate renovate bot changed the title Update dependency coverage to v7.6.2 Update dependency coverage to v7.6.3 Oct 13, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 8bc095a to 58b9321 Compare October 21, 2024 01:32
@renovate renovate bot changed the title Update dependency coverage to v7.6.3 Update dependency coverage to v7.6.4 Oct 21, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 58b9321 to e78d23a Compare November 14, 2024 18:26
@renovate renovate bot changed the title Update dependency coverage to v7.6.4 Update dependency coverage to v7.6.5 Nov 14, 2024
@renovate renovate bot changed the title Update dependency coverage to v7.6.5 Update dependency coverage to v7.6.6 Nov 15, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch 2 times, most recently from 4d10bbc to 3c262ff Compare November 15, 2024 16:30
@renovate renovate bot changed the title Update dependency coverage to v7.6.6 Update dependency coverage to v7.6.7 Nov 15, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 3c262ff to e919bdc Compare November 24, 2024 03:49
@renovate renovate bot changed the title Update dependency coverage to v7.6.7 Update dependency coverage to v7.6.8 Nov 24, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from e919bdc to c1b28eb Compare December 6, 2024 14:11
@renovate renovate bot changed the title Update dependency coverage to v7.6.8 Update dependency coverage to v7.6.9 Dec 6, 2024
Copy link

sonarqubecloud bot commented Dec 6, 2024

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

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.

0 participants