[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	7.16.2 → 7.17.1

---

Release Notes

coveragepy/coveragepy (coverage)

v7.17.1

Compare Source

• Fix: a one-line class or function body immediately followed by another
  statement (such as class Foo: ... on its own line) was incorrectly
  reported as a missing branch when using the sys.monitoring core. This is now
  fixed, closing issue 2167_ and issue 2337_.

• Fix: the HTML report only rewrites a file's page when the file or its data
  has changed, but each page also links to the previous and next files. When
  the set of reported files changed, unchanged pages kept their old links. For
  example, with skip_covered, a file that became 100% covered had its page
  deleted, but the pages next to it still linked to it. Now a page is also
  rewritten when its neighbors change.

• Fix: --fail-under now uses at least the decimal precision of the
  threshold for both the comparison and failure message. With precision=0,
  a total of 0.4 now passes --fail-under=0.3 and fails --fail-under=0.5
  with the message "total of 0.4 is less than fail-under=0.5". Previously, the
  comparison rounded the total to zero and the message could claim "1 is less
  than 0". Closes issue 2295_.

• Fix: the HTML report escaped file names twice, so a name with &, <,
  or quotes in it was shown with entities like &. Now they are properly
  escaped only once.

• Fix: --source=/ measured no files. A file system root can't be a source
  directory, so now it is an error. Closes issue 2291_.

• In an abundance of caution, prevent forged SQLite journal files from deleting
  files they shouldn't.

.. _issue 2167: #​2167
.. _issue 2291: #​2291
.. _issue 2295: #​2295
.. _issue 2337: #​2337

.. _changes_7-17-0:

v7.17.0

Compare Source

• Dropped support for Python 3.10.

• Binary wheels are now provided for iOS and Android. This allows the use of
  the optimized C tracer on mobile platforms.

• Fix: three or more levels of nested with statements could make a with
  line look like a branch with an exit that can never happen. Using the
  sys.monitoring core, these phantom branches were reported as partial. Other
  cores hid the problem but still counted the phantom branches in the total.
  Closes issue 1987_.

• Fix: a comment or string that merely mentioned if True: or
  while True: could mark its line as a branch that is known to be partial,
  so a branch that never ran was reported as taken. These built-in patterns
  now only match at the start of the statement. Closes issue 2314_.

• Fix: region detection missed functions defined in unusual places, such as
  else and except clauses. This is now fixed.

• Fix: recent versions of the lcov tool complain if the same function name
  appears more than once in a report. Python can have multiple same-named
  functions in a few ways, for example, getters/setters or conditionally
  defined functions. These are now disambiguated by adding a @<line number>
  suffix to the function name. Fixes issue 2335.

• Fix: The "Can't combine statement coverage data with branch data" error now
  names the two data files it couldn't combine. The :ref:error description <error_cant_combine> in the docs now lists common causes and how to find the
  process that wrote the file.

• Fix: at coverage totals close to 0 or 100, the XML report could get incorrect
  line-rate values like 8.333e-05 or 1. This is now fixed, closing
  issue 2293_ and issue 2294_.

• Fix: a parallel data file saved more than once kept the hash of its first
  save in its file name. Combining could then skip it as a duplicate of another
  file that had the same data at that point, and delete it, losing the data
  recorded after the first save. Each save now updates the hash. This had been
  a problem since 7.13.1. Fixes issue 2338_.

• Fixes for obscure but legal file names:

  • File names (and plugin names) can contain control characters, which are
    legal in POSIX paths but unsafe in reports: in XML 1.0 they make the
    document non-well-formed, and in a terminal they act as escape sequences
    (colors, title/clipboard sequences, cursor moves that forge output). Now
    the XML report, the text and Markdown summary reports, and coverage debug data replace non-printable characters in names. Printable names are
    unchanged.

  • A file pattern (from include, omit, or a [paths] alias)
    containing a newline sent the glob-to-regex translation into an infinite
    loop, hanging the process. Newlines in patterns are now handled like any
    other character.

• Fixes in the implementation of the C tracer:

  • If a plugin's dynamic_source_filename method raised an exception, lines
    in that function could be recorded as belonging to a different file. Also
    fixed some minor memory leaks in the C tracer.

  • The refcount of None was mismanaged during function calls, including
    comprehensions. This was unlikely to cause an actual problem, but is now
    fixed. Thanks, Andrew Dalke.

  • The C tracer held borrowed references to dictionary values, which was
    unsafe on free-threaded Python. Now it takes its own references.

  • An internal error while recording a new file could be reported as a
    confusing SystemError instead of the actual exception.

• Performance: the text summary report (coverage report) held on to every
  file's parsed source until it finished, so its memory use grew with the size
  of the project: ten times or more what 7.14 used on large projects. Now it
  keeps only what it needs to print. Fixes issue 2277_.

• Performance: HTML reports should be about 5% faster to produce.

• Kept the political banner in the README. Closes issue 2344_.

.. _issue 1987: #​1987
.. _issue 2277: #​2277
.. _issue 2293: #​2293
.. _issue 2294: #​2294
.. _issue 2314: #​2314
.. _issue 2335: #​2335
.. _issue 2338: #​2338
.. _issue 2344: #​2344

.. _changes_7-16-2:

---

Configuration

📅 Schedule: (UTC)

• 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 is behind base branch, 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.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (d1a932c)	559	559	100.00%
Head commit (c84d0e9)	559 (+0)	559 (+0)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#860)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (9ad4bdb) to head (c84d0e9).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #860   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          559       559           
  Branches        41        41           
=========================================
  Hits           559       559           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud