search

ctalkington / python-ipp

Asynchronous Python client for Internet Printing Protocol (IPP)
MIT License
36 stars 20 forks source link

Update dependency coverage to v7.6.2 #581

Closed renovate[bot] closed 1 month ago

renovate[bot] commented 6 months ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
coverage 7.5.1 -> 7.6.2 age adoption passing confidence

Release Notes

nedbat/coveragepy (coverage) ### [`v7.6.2`](https://redirect.github.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-762--2024-10-09) [Compare Source](https://redirect.github.com/nedbat/coveragepy/compare/7.6.1...7.6.2) - 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. - 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 `*. - 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 \` 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 `*. .. \_issue 1835:[https://github.com/nedbat/coveragepy/issues/1835](https://redirect.github.com/nedbat/coveragepy/issues/1835)5 .. \_issue 1836[https://github.com/nedbat/coveragepy/issues/1836](https://redirect.github.com/nedbat/coveragepy/issues/1836)36 .. \_pull 183[https://github.com/nedbat/coveragepy/pull/1838](https://redirect.github.com/nedbat/coveragepy/pull/1838)838 .. \_pull 18[https://github.com/nedbat/coveragepy/pull/1843](https://redirect.github.com/nedbat/coveragepy/pull/1843)1843 .. \_issue 1[https://github.com/nedbat/coveragepy/issues/1846](https://redirect.github.com/nedbat/coveragepy/issues/1846)/1846 .. \_pull [https://github.com/nedbat/coveragepy/pull/1849](https://redirect.github.com/nedbat/coveragepy/pull/1849)l/1849 .. \_issue[https://github.com/nedbat/coveragepy/issues/1850](https://redirect.github.com/nedbat/coveragepy/issues/1850)es/1850 .. \_pul[https://github.com/nedbat/coveragepy/pull/1851](https://redirect.github.com/nedbat/coveragepy/pull/1851)ull/1851 .. \_iss[https://github.com/nedbat/coveragepy/issues/1860](https://redirect.github.com/nedbat/coveragepy/issues/1860)sues/1860 .. \_is[https://github.com/nedbat/coveragepy/issues/1863](https://redirect.github.com/nedbat/coveragepy/issues/1863)ssues/1863 .. \_changes\_7-6-1: ### [`v7.6.1`](https://redirect.github.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-761--2024-08-04) [Compare Source](https://redirect.github.com/nedbat/coveragepy/compare/7.6.0...7.6.1) - Fix: coverage used to fail when measuring code using :func:`runpy.run_path ` with a :class:`Path ` argument. This is now fixed, thanks to `Ask Hjorth Larsen `\_. - Fix: backslashes preceding a multi-line backslashed string could confuse the HTML report. This is now fixed, thanks to `LiuYinCarl `\_. - Now we publish wheels for Python 3.13, both regular and free-threaded. .. \_pull 1819:[https://github.com/nedbat/coveragepy/pull/1819](https://redirect.github.com/nedbat/coveragepy/pull/1819)9 .. \_pull 1828[https://github.com/nedbat/coveragepy/pull/1828](https://redirect.github.com/nedbat/coveragepy/pull/1828)28 .. \_changes\_7-6-0: ### [`v7.6.0`](https://redirect.github.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-760--2024-07-11) [Compare Source](https://redirect.github.com/nedbat/coveragepy/compare/7.5.4...7.6.0) - Exclusion patterns can now be multi-line, thanks to `Daniel Diniz `*. This enables many interesting exclusion use-cases, including those requested in issues `118 `* (entire files), `996 `\_ (multiple lines only when appearing together), `1741 `\_ (remainder of a function), and `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 `\_ 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/118](https://redirect.github.com/nedbat/coveragepy/issues/118)8 .. \_issue 996[https://github.com/nedbat/coveragepy/issues/996](https://redirect.github.com/nedbat/coveragepy/issues/996)96 .. \_issue 153[https://github.com/nedbat/coveragepy/issues/1532](https://redirect.github.com/nedbat/coveragepy/issues/1532)532 .. \_issue 17[https://github.com/nedbat/coveragepy/issues/1741](https://redirect.github.com/nedbat/coveragepy/issues/1741)1741 .. \_issue 1[https://github.com/nedbat/coveragepy/issues/1793](https://redirect.github.com/nedbat/coveragepy/issues/1793)/1793 .. \_issue [https://github.com/nedbat/coveragepy/issues/1803](https://redirect.github.com/nedbat/coveragepy/issues/1803)s/1803 .. \_pull[https://github.com/nedbat/coveragepy/pull/1807](https://redirect.github.com/nedbat/coveragepy/pull/1807)ll/1807 .. \_pul[https://github.com/nedbat/coveragepy/pull/1809](https://redirect.github.com/nedbat/coveragepy/pull/1809)ull/1809 .. \_changes\_7-5-4: ### [`v7.5.4`](https://redirect.github.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-754--2024-06-22) [Compare Source](https://redirect.github.com/nedbat/coveragepy/compare/7.5.3...7.5.4) - 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/1799](https://redirect.github.com/nedbat/coveragepy/issues/1799)9 .. \_changes\_7-5-3: ### [`v7.5.3`](https://redirect.github.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-753--2024-05-28) [Compare Source](https://redirect.github.com/nedbat/coveragepy/compare/7.5.2...7.5.3) - 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/1791](https://redirect.github.com/nedbat/coveragepy/issues/1791)1 .. \_changes\_7-5-2: ### [`v7.5.2`](https://redirect.github.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-752--2024-05-24) [Compare Source](https://redirect.github.com/nedbat/coveragepy/compare/7.5.1...7.5.2) - 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 `\_. - 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 `*. Closes `issue 1787`*. .. \_pull 1776:[https://github.com/nedbat/coveragepy/pull/1776](https://redirect.github.com/nedbat/coveragepy/pull/1776)6 .. \_issue 1779[https://github.com/nedbat/coveragepy/issues/1779](https://redirect.github.com/nedbat/coveragepy/issues/1779)79 .. \_issue 178[https://github.com/nedbat/coveragepy/issues/1787](https://redirect.github.com/nedbat/coveragepy/issues/1787)787 .. \_pull 17[https://github.com/nedbat/coveragepy/pull/1788](https://redirect.github.com/nedbat/coveragepy/pull/1788)1788 .. \_changes\_7-5-1:

Configuration

📅 Schedule: Branch creation - "before 4am" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

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

codecov[bot] commented 6 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.59%. Comparing base (d5b9edc) to head (a409604). Report is 1 commits behind head on master.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #581 +/- ## ======================================= Coverage 94.59% 94.59% ======================================= Files 9 9 Lines 870 870 Branches 133 121 -12 ======================================= Hits 823 823 Misses 20 20 Partials 27 27 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.