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

chore(deps): update dependency coverage to v7.6.10 #223

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 14, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
coverage 7.6.4 -> 7.6.10 age adoption passing confidence

Release Notes

nedbat/coveragepy (coverage)

v7.6.10

Compare Source

  • Fix: some descriptions of missing branches in HTML and LCOV reports were
    incorrect when multi-line statements were involved (issue 1874_ and issue 1875_). These are now fixed.

  • Fix: Python 3.14 defers evaluation of annotations <pep649_>_ by moving them
    into separate code objects. That code is rarely executed, so coverage.py
    would mark them as missing, as reported in issue 1908_. Now they are
    ignored by coverage automatically.

  • Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
    mocks, imports, and trace functions: issue 1902_. To be honest, I don't
    understand the problem or the solution, but git bisect helped find it,
    and now it's fixed.

  • Docs: re-wrote the :ref:subprocess page to put multiprocessing first and to
    highlight the correct use of :class:multiprocessing.Pool <python:multiprocessing.pool.Pool>.

.. _issue 1874:https://github.com/nedbat/coveragepy/issues/18744
.. _issue 1875https://github.com/nedbat/coveragepy/issues/187575
.. _issue 190https://github.com/nedbat/coveragepy/issues/1902902
.. _issue 19https://github.com/nedbat/coveragepy/issues/19081908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#pep-649-deferred-evaluation-of-annotations

.. _changes_7-6-9:

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:


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 changed the title chore(deps): update dependency coverage to v7.6.5 chore(deps): update dependency coverage to v7.6.6 Nov 15, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from e083571 to cb84155 Compare November 15, 2024 13:44
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.6.6 chore(deps): update dependency coverage to v7.6.7 Nov 15, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from cb84155 to 5d9c527 Compare November 15, 2024 15:37
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.6.7 chore(deps): update dependency coverage to v7.6.8 Nov 24, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 5d9c527 to fe39afc Compare November 24, 2024 03:29
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.6.8 chore(deps): update dependency coverage to v7.6.9 Dec 6, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from fe39afc to 1f59adf Compare December 6, 2024 14:18
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.6.9 chore(deps): update dependency coverage to v7.6.10 Dec 26, 2024
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 1f59adf to e16d779 Compare December 26, 2024 19:01
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