Scheduled monthly dependency update for February #238

pyup-bot · 2024-02-01T19:03:08Z

Update coverage from 6.3.2 to 7.4.1.

Changelog

7.4.1

-   Python 3.13.0a3 is supported.
-   Fix: the JSON report now includes an explicit format version number, closing [issue 1732](https://github.com/nedbat/coveragepy/issues/1732).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.4.1](https://pypi.org/project/coverage/7.4.1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.4.1`

7.4.0

-   In Python 3.12 and above, you can try an experimental core based on the new `sys.monitoring &lt;python:sys.monitoring&gt;` module by defining a `COVERAGE_CORE=sysmon` environment variable. This should be faster for line coverage, but not for branch coverage, and plugins and dynamic contexts are not yet supported with it. I am very interested to hear how it works (or doesn&#x27;t!) for you.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.4.0](https://pypi.org/project/coverage/7.4.0).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.4.0`

7.3.4

-   Fix: the change for multi-line signature exclusions in 7.3.3 broke other forms of nested clauses being excluded properly. This is now fixed, closing [issue 1713](https://github.com/nedbat/coveragepy/issues/1713).
-   Fix: in the HTML report, selecting code for copying won&#x27;t select the line numbers also. Thanks, [Robert Harris](https://github.com/nedbat/coveragepy/pull/1717).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.3.4](https://pypi.org/project/coverage/7.3.4).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.3.4`

7.3.3

-   Fix: function definitions with multi-line signatures can now be excluded by matching any of the lines, closing [issue 684](https://github.com/nedbat/coveragepy/issues/684). Thanks, [Jan Rusak, Maciej Kowalczyk and Joanna Ejzel](https://github.com/nedbat/coveragepy/pull/1705).
-   Fix: XML reports could fail with a TypeError if files had numeric components that were duplicates except for leading zeroes, like `file1.py` and `file001.py`. Fixes [issue 1709](https://github.com/nedbat/coveragepy/issues/1709).
-   The `coverage annotate` command used to announce that it would be removed in a future version. Enough people got in touch to say that they use it, so it will stay. Don&#x27;t expect it to keep up with other new features though.
-   Added new `debug options &lt;cmd_run_debug&gt;`:
 -   `pytest` writes the pytest test name into the debug output.
 -   `dataop2` writes the full data being added to CoverageData objects.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.3.3](https://pypi.org/project/coverage/7.3.3).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.3.3`

7.3.2

-   The `coverage lcov` command ignored the `[report] exclude_lines` and `[report] exclude_also` settings ([issue 1684](https://github.com/nedbat/coveragepy/issues/1684)). This is now fixed, thanks [Jacqueline Lee](https://github.com/nedbat/coveragepy/pull/1685).
-   Sometimes SQLite will create journal files alongside the coverage.py database files. These are ephemeral, but could be mistakenly included when combining data files. Now they are always ignored, fixing [issue 1605](https://github.com/nedbat/coveragepy/issues/1605). Thanks to Brad Smith for suggesting fixes and providing detailed debugging.
-   On Python 3.12+, we now disable SQLite writing journal files, which should be a little faster.
-   The new 3.12 soft keyword `type` is properly bolded in HTML reports.
-   Removed the &quot;fullcoverage&quot; feature used by CPython to measure the coverage of early-imported standard library modules. CPython [stopped using it](https://github.com/python/cpython/issues/88054) in 2021, and it stopped working completely in Python 3.13.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.3.2](https://pypi.org/project/coverage/7.3.2).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.3.2`

7.3.1

-   The semantics of stars in file patterns has been clarified in the docs. A leading or trailing star matches any number of path components, like a double star would. This is different than the behavior of a star in the middle of a pattern. This discrepancy was [identified by Sviatoslav Sydorenko](https://github.com/nedbat/coveragepy/issues/1407#issuecomment-1631085209), who [provided patient detailed diagnosis](https://github.com/nedbat/coveragepy/pull/1650) and graciously agreed to a pragmatic resolution.
-   The API docs were missing from the last version. They are now [restored](https://coverage.readthedocs.io/en/latest/api_coverage.html).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.3.1](https://pypi.org/project/coverage/7.3.1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.3.1`

7.3.0

-   Added a `.Coverage.collect` context manager to start and stop coverage data collection.
-   Dropped support for Python 3.7.
-   Fix: in unusual circumstances, SQLite cannot be set to asynchronous mode. Coverage.py would fail with the error `Safety level may not be changed inside a transaction.` This is now avoided, closing [issue 1646](https://github.com/nedbat/coveragepy/issues/1646). Thanks to Michael Bell for the detailed bug report.
-   Docs: examples of configuration files now include separate examples for the different syntaxes: .coveragerc, pyproject.toml, setup.cfg, and tox.ini.
-   Fix: added `nosemgrep` comments to our JavaScript code so that semgrep-based SAST security checks won&#x27;t raise false alarms about security problems that aren&#x27;t problems.
-   Added a CITATION.cff file, thanks to [Ken Schackart](https://github.com/nedbat/coveragepy/pull/1641).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.3.0](https://pypi.org/project/coverage/7.3.0).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.3.0`

7.2.7

-   Fix: reverted a [change from 6.4.3](https://github.com/nedbat/coveragepy/pull/1347) that helped Cython, but also increased the size of data files when using dynamic contexts, as described in the now-fixed [issue 1586](https://github.com/nedbat/coveragepy/issues/1586). The problem is now avoided due to a recent change ([issue 1538](https://github.com/nedbat/coveragepy/issues/1538)). Thanks to [Anders Kaseorg](https://github.com/nedbat/coveragepy/pull/1629) and David Szotten for persisting with problem reports and detailed diagnoses.
-   Wheels are now provided for CPython 3.12.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.7](https://pypi.org/project/coverage/7.2.7).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.7`

7.2.6

-   Fix: the `lcov` command could raise an IndexError exception if a file is translated to Python but then executed under its own name. Jinja2 does this when rendering templates. Fixes [issue 1553](https://github.com/nedbat/coveragepy/issues/1553).
-   Python 3.12 beta 1 now inlines comprehensions. Previously they were compiled as invisible functions and coverage.py would warn you if they weren&#x27;t completely executed. This no longer happens under Python 3.12.
-   Fix: the `coverage debug sys` command includes some environment variables in its output. This could have included sensitive data. Those values are now hidden with asterisks, closing [issue 1628](https://github.com/nedbat/coveragepy/issues/1628).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.6](https://pypi.org/project/coverage/7.2.6).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.6`

7.2.5

-   Fix: `html_report()` could fail with an AttributeError on `isatty` if run in an unusual environment where sys.stdout had been replaced. This is now fixed.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.5](https://pypi.org/project/coverage/7.2.5).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.5`

7.2.4

PyCon 2023 sprint fixes!

-   Fix: with `relative_files = true`, specifying a specific file to include or omit wouldn&#x27;t work correctly ([issue 1604](https://github.com/nedbat/coveragepy/issues/1604)). This is now fixed, with testing help by [Marc Gibbons](https://github.com/nedbat/coveragepy/pull/1608).
-   Fix: the XML report would have an incorrect `&lt;source&gt;` element when using relative files and the source option ended with a slash ([issue 1541](https://github.com/nedbat/coveragepy/issues/1541)). This is now fixed, thanks to [Kevin Brown-Silva](https://github.com/nedbat/coveragepy/pull/1608).
-   When the HTML report location is printed to the terminal, it&#x27;s now a terminal-compatible URL, so that you can click the location to open the HTML file in your browser. Finishes [issue 1523](https://github.com/nedbat/coveragepy/issues/1523) thanks to [Ricardo Newbery](https://github.com/nedbat/coveragepy/pull/1613).
-   Docs: a new `Migrating page &lt;migrating&gt;` with details about how to migrate between major versions of coverage.py. It currently covers the wildcard changes in 7.x. Thanks, [Brian Grohe](https://github.com/nedbat/coveragepy/pull/1610).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.4](https://pypi.org/project/coverage/7.2.4).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.4`

7.2.3

-   Fix: the `config_run_sigterm` setting was meant to capture data if a process was terminated with a SIGTERM signal, but it didn&#x27;t always. This was fixed thanks to [Lewis Gaul](https://github.com/nedbat/coveragepy/pull/1600), closing [issue 1599](https://github.com/nedbat/coveragepy/issues/1599).
-   Performance: HTML reports with context information are now much more compact. File sizes are typically as small as one-third the previous size, but can be dramatically smaller. This closes [issue 1584](https://github.com/nedbat/coveragepy/issues/1584) thanks to [Oleh Krehel](https://github.com/nedbat/coveragepy/pull/1587).
-   Development dependencies no longer use hashed pins, closing [issue 1592](https://github.com/nedbat/coveragepy/issues/1592).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.3](https://pypi.org/project/coverage/7.2.3).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.3`

7.2.2

-   Fix: if a virtualenv was created inside a source directory, and a sourced package was installed inside the virtualenv, then all of the third-party packages inside the virtualenv would be measured. This was incorrect, but has now been fixed: only the specified packages will be measured, thanks to [Manuel Jacob](https://github.com/nedbat/coveragepy/pull/1560).
-   Fix: the `coverage lcov` command could create a .lcov file with incorrect LF (lines found) and LH (lines hit) totals. This is now fixed, thanks to [Ian Moore](https://github.com/nedbat/coveragepy/pull/1583).
-   Fix: the `coverage xml` command on Windows could create a .xml file with duplicate `&lt;package&gt;` elements. This is now fixed, thanks to [Benjamin Parzella](https://github.com/nedbat/coveragepy/pull/1574), closing [issue 1573](https://github.com/nedbat/coveragepy/issues/1573).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.2](https://pypi.org/project/coverage/7.2.2).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.2`

7.2.1

-   Fix: the PyPI page had broken links to documentation pages, but no longer does, closing [issue 1566](https://github.com/nedbat/coveragepy/issues/1566).
-   Fix: public members of the coverage module are now properly indicated so that mypy will find them, fixing [issue 1564](https://github.com/nedbat/coveragepy/issues/1564).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.1](https://pypi.org/project/coverage/7.2.1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.1`

7.2.0

-   Added a new setting `[report] exclude_also` to let you add more exclusions without overwriting the defaults. Thanks, [Alpha Chen](https://github.com/nedbat/coveragepy/pull/1557), closing [issue 1391](https://github.com/nedbat/coveragepy/issues/1391).
-   Added a `.CoverageData.purge_files` method to remove recorded data for a particular file. Contributed by [Stephan Deibel](https://github.com/nedbat/coveragepy/pull/1547).
-   Fix: when reporting commands fail, they will no longer congratulate themselves with messages like &quot;Wrote XML report to file.xml&quot; before spewing a traceback about their failure.
-   Fix: arguments in the public API that name file paths now accept pathlib.Path objects. This includes the `data_file` and `config_file` arguments to the Coverage constructor and the `basename` argument to CoverageData. Closes [issue 1552](https://github.com/nedbat/coveragepy/issues/1552).
-   Fix: In some embedded environments, an IndexError could occur on stop() when the originating thread exits before completion. This is now fixed, thanks to [Russell Keith-Magee](https://github.com/nedbat/coveragepy/pull/1543), closing [issue 1542](https://github.com/nedbat/coveragepy/issues/1542).
-   Added a `py.typed` file to announce our type-hintedness. Thanks, [KotlinIsland](https://github.com/nedbat/coveragepy/pull/1550).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.2.0](https://pypi.org/project/coverage/7.2.0).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.2.0`

7.1.0

-   Added: the debug output file can now be specified with `[run] debug_file` in the configuration file. Closes [issue 1319](https://github.com/nedbat/coveragepy/issues/1319).
-   Performance: fixed a slowdown with dynamic contexts that&#x27;s been around since 6.4.3. The fix closes [issue 1538](https://github.com/nedbat/coveragepy/issues/1538). Thankfully this doesn&#x27;t break the [Cython change](https://github.com/nedbat/coveragepy/pull/1347) that fixed [issue 972](https://github.com/nedbat/coveragepy/issues/972). Thanks to Mathieu Kniewallner for the deep investigative work and comprehensive issue report.
-   Typing: all product and test code has type annotations.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.1.0](https://pypi.org/project/coverage/7.1.0).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.1.0`

7.0.5

-   Fix: On Python 3.7, a file with type annotations but no `from __future__ import annotations` would be missing statements in the coverage report. This is now fixed, closing [issue 1524](https://github.com/nedbat/coveragepy/issues/1524).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.5](https://pypi.org/project/coverage/7.0.5).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.5`

7.0.4

-   Performance: an internal cache of file names was accidentally disabled, resulting in sometimes drastic reductions in performance. This is now fixed, closing [issue 1527](https://github.com/nedbat/coveragepy/issues/1527). Thanks to Ivan Ciuvalschii for the reproducible test case.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.4](https://pypi.org/project/coverage/7.0.4).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.4`

7.0.3

-   Fix: when using pytest-cov or pytest-xdist, or perhaps both, the combining step could fail with `assert row is not None` using 7.0.2. This was due to a race condition that has always been possible and is still possible. In 7.0.1 and before, the error was silently swallowed by the combining code. Now it will produce a message &quot;Couldn&#x27;t combine data file&quot; and ignore the data file as it used to do before 7.0.2. Closes [issue 1522](https://github.com/nedbat/coveragepy/issues/1522).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.3](https://pypi.org/project/coverage/7.0.3).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.3`

7.0.2

-   Fix: when using the `[run] relative_files = True` setting, a relative `[paths]` pattern was still being made absolute. This is now fixed, closing [issue 1519](https://github.com/nedbat/coveragepy/issues/1519).
-   Fix: if Python doesn&#x27;t provide tomllib, then TOML configuration files can only be read if coverage.py is installed with the `[toml]` extra. Coverage.py will raise an error if TOML support is not installed when it sees your settings are in a .toml file. But it didn&#x27;t understand that `[tools.coverage]` was a valid section header, so the error wasn&#x27;t reported if you used that header, and settings were silently ignored. This is now fixed, closing [issue 1516](https://github.com/nedbat/coveragepy/issues/1516).
-   Fix: adjusted how decorators are traced on PyPy 7.3.10, fixing [issue 1515](https://github.com/nedbat/coveragepy/issues/1515).
-   Fix: the `coverage lcov` report did not properly implement the `--fail-under=MIN` option. This has been fixed.
-   Refactor: added many type annotations, including a number of refactorings. This should not affect outward behavior, but they were a bit invasive in some places, so keep your eyes peeled for oddities.
-   Refactor: removed the vestigial and long untested support for Jython and IronPython.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.2](https://pypi.org/project/coverage/7.0.2).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.2`

7.0.1

-   When checking if a file mapping resolved to a file that exists, we weren&#x27;t considering files in .whl files. This is now fixed, closing [issue 1511](https://github.com/nedbat/coveragepy/issues/1511).
-   File pattern rules were too strict, forbidding plus signs and curly braces in directory and file names. This is now fixed, closing [issue 1513](https://github.com/nedbat/coveragepy/issues/1513).
-   Unusual Unicode or control characters in source files could prevent reporting. This is now fixed, closing [issue 1512](https://github.com/nedbat/coveragepy/issues/1512).
-   The PyPy wheel now installs on PyPy 3.7, 3.8, and 3.9, closing [issue 1510](https://github.com/nedbat/coveragepy/issues/1510).


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.1](https://pypi.org/project/coverage/7.0.1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.1`

7.0.0

Nothing new beyond 7.0.0b1.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.0](https://pypi.org/project/coverage/7.0.0).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.0`

7.0.0b1

A number of changes have been made to file path handling, including pattern matching and path remapping with the `[paths]` setting (see `config_paths`). These changes might affect you, and require you to update your settings.

(This release includes the changes from [6.6.0b1](https://coverage.readthedocs.io/en/latest/changes.html#changes-6-6-0b1), since 6.6.0 was never released.)

-   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](https://github.com/nedbat/coveragepy/issues/1407).
 -   Now `**` matches any number of nested directories, including none.
-   Improvements to combining data files when using the `config_run_relative_files` setting, which might require updating your configuration:
 -   During `coverage combine`, relative file paths are implicitly combined without needing a `[paths]` configuration setting. This also fixed [issue 991](https://github.com/nedbat/coveragepy/issues/991).
 -   A `[paths]` setting like `*/foo` will now match `foo/bar.py` so that relative file paths can be combined more easily.
 -   The `config_run_relative_files` setting is properly interpreted in more places, fixing [issue 1280](https://github.com/nedbat/coveragepy/issues/1280).
-   When remapping file paths with `[paths]`, a path will be remapped only if the resulting path exists. The documentation has long said the prefix had to exist, but it was never enforced. This fixes [issue 608](https://github.com/nedbat/coveragepy/issues/608), improves [issue 649](https://github.com/nedbat/coveragepy/issues/649), and closes [issue 757](https://github.com/nedbat/coveragepy/issues/757).
-   Reporting operations now implicitly use the `[paths]` setting to remap file paths within a single data file. Combining multiple files still requires the `coverage combine` step, but this simplifies some single-file situations. Closes [issue 1212](https://github.com/nedbat/coveragepy/issues/1212) and [issue 713](https://github.com/nedbat/coveragepy/issues/713).
-   The `coverage report` command now has a `--format=` option. The original style is now `--format=text`, and is the default.
 -   Using `--format=markdown` will write the table in Markdown format, thanks to [Steve Oswald](https://github.com/nedbat/coveragepy/pull/1479), closing [issue 1418](https://github.com/nedbat/coveragepy/issues/1418).
 -   Using `--format=total` will write a single total number to the output. This can be useful for making badges or writing status updates.
-   Combining data files with `coverage combine` now hashes the data files to skip files that add no new information. This can reduce the time needed. Many details affect the speed-up, but for coverage.py&#x27;s own test suite, combining is about 40% faster. Closes [issue 1483](https://github.com/nedbat/coveragepy/issues/1483).
-   When searching for completely un-executed files, coverage.py uses the presence of `__init__.py` files to determine which directories have source that could have been imported. However, [implicit namespace packages](https://peps.python.org/pep-0420/) don&#x27;t require `__init__.py`. A new setting `[report] include_namespace_packages` tells coverage.py to consider these directories during reporting. Thanks to [Felix Horvat](https://github.com/nedbat/coveragepy/pull/1387) for the contribution. Closes [issue 1383](https://github.com/nedbat/coveragepy/issues/1383) and [issue 1024](https://github.com/nedbat/coveragepy/issues/1024).
-   Fixed environment variable expansion in pyproject.toml files. It was overly broad, causing errors outside of coverage.py settings, as described in [issue 1481](https://github.com/nedbat/coveragepy/issues/1481) and [issue 1345](https://github.com/nedbat/coveragepy/issues/1345). This is now fixed, but in rare cases will require changing your pyproject.toml to quote non-string values that use environment substitution.
-   An empty file has a coverage total of 100%, but used to fail with `--fail-under`. This has been fixed, closing [issue 1470](https://github.com/nedbat/coveragepy/issues/1470).
-   The text report table no longer writes out two separator lines if there are no files listed in the table. One is plenty.
-   Fixed a mis-measurement of a strange use of wildcard alternatives in match/case statements, closing [issue 1421](https://github.com/nedbat/coveragepy/issues/1421).
-   Fixed internal logic that prevented coverage.py from running on implementations other than CPython or PyPy ([issue 1474](https://github.com/nedbat/coveragepy/issues/1474)).
-   The deprecated `[run] note` setting has been completely removed.


:arrow_right:&amp;nbsp; PyPI page: [coverage 7.0.0b1](https://pypi.org/project/coverage/7.0.0b1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==7.0.0b1`

6.6.0b1

(Note: 6.6.0 final was never released. These changes are part of [7.0.0b1](https://coverage.readthedocs.io/en/latest/changes.html#changes-7-0-0b1).)

-   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](https://github.com/nedbat/coveragepy/issues/1407).
 -   Now `**` matches any number of nested directories, including none.
-   Improvements to combining data files when using the `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](https://github.com/nedbat/coveragepy/issues/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](https://github.com/nedbat/coveragepy/issues/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](https://github.com/nedbat/coveragepy/issues/1481) and [issue 1345](https://github.com/nedbat/coveragepy/issues/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](https://github.com/nedbat/coveragepy/issues/1474)).


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.6.0b1](https://pypi.org/project/coverage/6.6.0b1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.6.0b1`

6.5.0

-   The JSON report now includes details of which branches were taken, and which are missing for each file. Thanks, [Christoph Blessing](https://github.com/nedbat/coveragepy/pull/1438). Closes [issue 1425](https://github.com/nedbat/coveragepy/issues/1425).
-   Starting with coverage.py 6.2, `class` statements were marked as a branch. This wasn&#x27;t right, and has been reverted, fixing [issue 1449](https://github.com/nedbat/coveragepy/issues/1449). Note this will very slightly reduce your coverage total if you are measuring branch coverage.
-   Packaging is now compliant with [PEP 517](https://peps.python.org/pep-0517/), closing [issue 1395](https://github.com/nedbat/coveragepy/issues/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](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381).


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.5.0](https://pypi.org/project/coverage/6.5.0).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.5.0`

6.4.4

-   Wheels are now provided for Python 3.11.


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.4.4](https://pypi.org/project/coverage/6.4.4).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.4.4`

6.4.3

-   Fix a failure when combining data files if the file names contained glob-like patterns. Thanks, [Michael Krebs and Benjamin Schubert](https://github.com/nedbat/coveragepy/issues/1405).
-   Fix a messaging failure when combining Windows data files on a different drive than the current directory, closing [issue 1428](https://github.com/nedbat/coveragepy/issues/1428). Thanks, [Lorenzo Micò](https://github.com/nedbat/coveragepy/pull/1430).
-   Fix path calculations when running in the root directory, as you might do in a Docker container. Thanks [Arthur Rio](https://github.com/nedbat/coveragepy/issues/1403).
-   Filtering in the HTML report wouldn&#x27;t work when reloading the index page. This is now fixed. Thanks, [Marc Legendre](https://github.com/nedbat/coveragepy/issues/1413).
-   Fix a problem with Cython code measurement, closing [issue 972](https://github.com/nedbat/coveragepy/issues/972). Thanks, [Matus Valo](https://github.com/nedbat/coveragepy/pull/1347).


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.4.3](https://pypi.org/project/coverage/6.4.3).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.4.3`

6.4.2

-   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 cannot 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](https://github.com/nedbat/coveragepy/issues/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](https://github.com/nedbat/coveragepy/pull/1399).


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.4.2](https://pypi.org/project/coverage/6.4.2).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.4.2`

6.4.1

-   Greatly improved performance on PyPy, and other environments that need the pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick ([pull 1381](https://github.com/nedbat/coveragepy/pull/1381) and [pull 1388](https://github.com/nedbat/coveragepy/pull/1388)). Slightly improved performance when using the C trace function, as most environments do. Closes [issue 1339](https://github.com/nedbat/coveragepy/issues/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](https://github.com/nedbat/coveragepy/issues/1390).


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.4.1](https://pypi.org/project/coverage/6.4.1).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.4.1`

6.4

-   A new setting, `config_run_sigterm`, controls whether a SIGTERM signal handler is used. In 6.3, the signal handler was always installed, to capture data at unusual process ends. Unfortunately, this introduced other problems (see [issue 1310](https://github.com/nedbat/coveragepy/issues/1310)). Now the signal handler is only used if you opt-in by setting `[run] sigterm = true`.
-   Small changes to the HTML report:
 -   Added links to next and previous file, and more keyboard shortcuts: `[` and `]` for next file and previous file; `u` for up to the index; and `?` to open/close the help panel. Thanks, [J. M. F. Tsang](https://github.com/nedbat/coveragepy/pull/1364).
 -   The time stamp and version are displayed at the top of the report. Thanks, [Ammar Askar](https://github.com/nedbat/coveragepy/pull/1354). Closes [issue 1351](https://github.com/nedbat/coveragepy/issues/1351).
-   A new debug option `debug=sqldata` adds more detail to `debug=sql`, logging all the data being written to the database.
-   Previously, running `coverage report` (or any of the reporting commands) in an empty directory would create a .coverage data file. Now they do not, fixing [issue 1328](https://github.com/nedbat/coveragepy/issues/1328).
-   On Python 3.11, the `[toml]` extra no longer installs tomli, instead using tomllib from the standard library. Thanks [Shantanu](https://github.com/nedbat/coveragepy/pull/1359).
-   In-memory CoverageData objects now properly update(), closing [issue 1323](https://github.com/nedbat/coveragepy/issues/1323).


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.4](https://pypi.org/project/coverage/6.4).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.4`

6.3.3

-   Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again. Closes [issue 1367](https://github.com/nedbat/coveragepy/issues/1367). Some results for generators may have changed.


:arrow_right:&amp;nbsp; PyPI page: [coverage 6.3.3](https://pypi.org/project/coverage/6.3.3).
:arrow_right:&amp;nbsp; To install: `python3 -m pip install coverage==6.3.3`

Links

PyPI: https://pypi.org/project/coverage
Changelog: https://data.safetycli.com/changelogs/coverage/
Repo: https://github.com/nedbat/coveragepy

Update flake8 from 4.0.1 to 7.0.0.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/flake8
Repo: https://github.com/pycqa/flake8

Update pre-commit from 2.17.0 to 3.6.0.

Changelog

3.6.0

==================

Features
- Check `minimum_pre_commit_version` first when parsing configs.
 - 3092 PR by asottile.

Fixes
- Fix deprecation warnings for `importlib.resources`.
 - 3043 PR by asottile.
- Fix deprecation warnings for rmtree.
 - 3079 PR by edgarrmondragon.

Updating
- Drop support for python&lt;3.9.
 - 3042 PR by asottile.
 - 3093 PR by asottile.

3.5.0

==================

Features
- Improve performance of `check-hooks-apply` and `check-useless-excludes`.
 - 2998 PR by mxr.
 - 2935 issue by mxr.

Fixes
- Use `time.monotonic()` for more accurate hook timing.
 - 3024 PR by adamchainz.

Migrating
- Require npm 6.x+ for `language: node` hooks.
 - 2996 PR by RoelAdriaans.
 - 1983 issue by henryiii.

3.4.0

==================

Features
- Add `language: haskell`.
 - 2932 by alunduil.
- Improve cpu count detection when run under cgroups.
 - 2979 PR by jdb8.
 - 2978 issue by jdb8.

Fixes
- Handle negative exit codes from hooks receiving posix signals.
 - 2971 PR by chriskuehl.
 - 2970 issue by chriskuehl.

3.3.3

==================

Fixes
- Work around OS packagers setting `--install-dir` / `--bin-dir` in gem settings.
 - 2905 PR by jaysoffian.
 - 2799 issue by lmilbaum.

3.3.2

==================

Fixes
- Work around `r` on windows sometimes double-un-quoting arguments.
 - 2885 PR by lorenzwalthert.
 - 2870 issue by lorenzwalthert.

3.3.1

==================

Fixes
- Work around `git` partial clone bug for `autoupdate` on windows.
 - 2866 PR by asottile.
 - 2865 issue by adehad.

3.3.0

==================

Features
- Upgrade ruby-build.
 - 2846 PR by jalessio.
- Use blobless clone for faster autoupdate.
 - 2859 PR by asottile.
- Add `-j` / `--jobs` argument to `autoupdate` for parallel execution.
 - 2863 PR by asottile.
 - issue by gaborbernat.

3.2.2

==================

Fixes
- Fix support for swift &gt;= 5.8.
 - 2836 PR by edelabar.
 - 2835 issue by kgrobelny-intive.

3.2.1

==================

Fixes
- Fix `language_version` for `language: rust` without global `rustup`.
 - 2823 issue by daschuer.
 - 2827 PR by asottile.

3.2.0

==================

Features
- Allow `pre-commit`, `pre-push`, and `pre-merge-commit` as `stages`.
 - 2732 issue by asottile.
 - 2808 PR by asottile.
- Add `pre-rebase` hook support.
 - 2582 issue by BrutalSimplicity.
 - 2725 PR by mgaligniana.

Fixes
- Remove bulky cargo cache from `language: rust` installs.
 - 2820 PR by asottile.

3.1.1

==================

Fixes
- Fix `rust` with `language_version` and a non-writable host `RUSTUP_HOME`.
 - pre-commit-ci/issues173 by Swiftb0y.
 - 2788 by asottile.

3.1.0

==================

Fixes
- Fix `dotnet` for `.sln`-based hooks for dotnet&gt;=7.0.200.
 - 2763 PR by m-rsha.
- Prevent stashing when `diff` fails to execute.
 - 2774 PR by asottile.
 - 2773 issue by strubbly.
- Dependencies are no longer sorted in repository key.
 - 2776 PR by asottile.

Updating
- Deprecate `language: python_venv`.  Use `language: python` instead.
 - 2746 PR by asottile.
 - 2734 issue by asottile.

3.0.4

==================

Fixes
- Fix hook diff detection for files affected by `--textconv`.
 - 2743 PR by adamchainz.
 - 2743 issue by adamchainz.

3.0.3

==================

Fixes
- Revert &quot;Prevent local `Gemfile` from interfering with hook execution.&quot;.
 - 2739 issue by Roguelazer.
 - 2740 PR by asottile.

3.0.2

==================

Fixes
- Prevent local `Gemfile` from interfering with hook execution.
 - 2727 PR by asottile.
- Fix `language: r`, `repo: local` hooks
 - pre-commit-ci/issues107 by lorenzwalthert.
 - 2728 PR by asottile.

3.0.1

==================

Fixes
- Ensure coursier hooks are available offline after install.
 - 2723 PR by asottile.

3.0.0

==================

Features
- Make `language: golang` bootstrap `go` if not present.
 - 2651 PR by taoufik07.
 - 2649 issue by taoufik07.
- `language: coursier` now supports `additional_dependencies` and `repo: local`
 - 2702 PR by asottile.
- Upgrade `ruby-build` to `20221225`.
 - 2718 PR by jalessio.

Fixes
- Improve error message for invalid yaml for `pre-commit autoupdate`.
 - 2686 PR by asottile.
 - 2685 issue by CarstenGrohmann.
- `repo: local` no longer provisions an empty `git` repo.
 - 2699 PR by asottile.

Updating
- Drop support for python&lt;3.8
 - 2655 PR by asottile.
- Drop support for top-level list, use `pre-commit migrate-config` to update.
 - 2656 PR by asottile.
- Drop support for `sha` to specify revision, use `pre-commit migrate-config`
to update.
 - 2657 PR by asottile.
- Remove `pre-commit-validate-config` and `pre-commit-validate-manifest`, use
`pre-commit validate-config` and `pre-commit validate-manifest` instead.
 - 2658 PR by asottile.
- `language: golang` hooks must use `go.mod` to specify dependencies
 - 2672 PR by taoufik07.

2.21.0

===================

Features
- Require new-enough virtualenv to prevent 3.10 breakage
 - 2467 PR by asottile.
- Respect aliases with `SKIP` for environment install.
 - 2480 PR by kmARC.
 - 2478 issue by kmARC.
- Allow `pre-commit run --files` against unmerged paths.
 - 2484 PR by asottile.
- Also apply regex warnings to `repo: local` hooks.
 - 2524 PR by chrisRedwine.
 - 2521 issue by asottile.
- `rust` is now a &quot;first class&quot; language -- supporting `language_version` and
installation when not present.
 - 2534 PR by Holzhaus.
- `r` now uses more-reliable binary installation.
 - 2460 PR by lorenzwalthert.
- `GIT_ALLOW_PROTOCOL` is now passed through for git operations.
 - 2555 PR by asottile.
- `GIT_ASKPASS` is now passed through for git operations.
 - 2564 PR by mattp-.
- Remove `toml` dependency by using `cargo add` directly.
 - 2568 PR by m-rsha.
- Support `dotnet` hooks which have dotted prefixes.
 - 2641 PR by rkm.
 - 2629 issue by rkm.

Fixes
- Properly adjust `--commit-msg-filename` if run from a sub directory.
 - 2459 PR by asottile.
- Simplify `--intent-to-add` detection by using `git diff`.
 - 2580 PR by m-rsha.
- Fix `R.exe` selection on windows.
 - 2605 PR by lorenzwalthert.
 - 2599 issue by SInginc.
- Skip default `nuget` source when installing `dotnet` packages.
 - 2642 PR by rkm.

2.20.0

===================

Features
- Expose `source` and `object-name` (positional args) of `prepare-commit-msg`
hook as `PRE_COMMIT_COMIT_MSG_SOURCE` and `PRE_COMMIT_COMMIT_OBJECT_NAME`.
 - 2407 PR by M-Whitaker.
 - 2406 issue by M-Whitaker.

Fixes
- Fix `language: ruby` installs when `--user-install` is set in gemrc.
 - 2394 PR by narpfel.
 - 2393 issue by narpfel.
- Adjust pty setup for solaris.
 - 2390 PR by gaige.
 - 2389 issue by gaige.
- Remove unused `--config` option from `gc`, `sample-config`,
`validate-config`, `validate-manifest` sub-commands.
 - 2429 PR by asottile.

2.19.0

===================

Features
- Allow multiple outputs from `language: dotnet` hooks.
 - 2332 PR by WallucePinkham.
- Add more information to `healthy()` failure.
 - 2348 PR by asottile.
- Upgrade ruby-build.
 - 2342 PR by jalessio.
- Add `pre-commit validate-config` / `pre-commit validate-manifest` and
deprecate `pre-commit-validate-config` and `pre-commit-validate-manifest`.
 - 2362 PR by asottile.

Fixes
- Fix `pre-push` when pushed ref contains spaces.
 - 2345 PR by wwade.
 - 2344 issue by wwade.

Updating
- Change `pre-commit-validate-config` / `pre-commit-validate-manifest` to
`pre-commit validate-config` / `pre-commit validate-manifest`.
 - 2362 PR by asottile.

2.18.1

===================

Fixes
- Fix regression for `repo: local` hooks running `python&lt;3.7`
 - 2324 PR by asottile.

2.18.0

===================

Features
- Keep `GIT_HTTP_PROXY_AUTHMETHOD` in git environ.
 - 2272 PR by VincentBerthier.
 - 2271 issue by VincentBerthier.
- Support both `cs` and `coursier` executables for coursier hooks.
 - 2293 PR by Holzhaus.
- Include more information in errors for `language_version` /
`additional_dependencies` for languages which do not support them.
 -  2315 PR by asottile.
- Have autoupdate preferentially pick tags which look like versions when
there are multiple equivalent tags.
 - 2312 PR by mblayman.
 - 2311 issue by mblayman.
- Upgrade `ruby-build`.
 - 2319 PR by jalessio.
- Add top level `default_install_hook_types` which will be installed when
`--hook-types` is not specified in `pre-commit install`.
 - 2322 PR by asottile.

Fixes
- Fix typo in help message for `--from-ref` and `--to-ref`.
 - 2266 PR by leetrout.
- Prioritize binary builds for R dependencies.
 - 2277 PR by lorenzwalthert.
- Fix handling of git worktrees.
 - 2252 PR by daschuer.
- Fix handling of `$R_HOME` for R hooks.
 - 2301 PR by jeff-m-sullivan.
 - 2300 issue by jeff-m-sullivan.
- Fix a rare race condition in change stashing.
 - 2323 PR by asottile.
 - 2287 issue by ian-h-chamberlain.

Updating
- Remove python3.6 support.  Note that pre-commit still supports running hooks
written in older versions, but pre-commit itself requires python 3.7+.
 - 2215 PR by asottile.
- pre-commit has migrated from the `master` branch to `main`.
 - 2302 PR by asottile.

Links

PyPI: https://pypi.org/project/pre-commit
Changelog: https://data.safetycli.com/changelogs/pre-commit/
Repo: https://github.com/pre-commit/pre-commit

Update pytest from 7.0.1 to 8.0.0.

Changelog

8.0.0

=========================

Bug Fixes
---------

- `11842 &lt;https://github.com/pytest-dev/pytest/issues/11842&gt;`_: Properly escape the ``reason`` of a :ref:`skip &lt;pytest.mark.skip ref&gt;` mark when writing JUnit XML files.


- `11861 &lt;https://github.com/pytest-dev/pytest/issues/11861&gt;`_: Avoid microsecond exceeds ``1_000_000`` when using ``log-date-format`` with ``%f`` specifier, which might cause the test suite to crash.

8.0.0rc2

============================


Improvements
------------

- `11233 &lt;https://github.com/pytest-dev/pytest/issues/11233&gt;`_: Improvements to ``-r`` for xfailures and xpasses:

* Report tracebacks for xfailures when ``-rx`` is set.
* Report captured output for xpasses when ``-rX`` is set.
* For xpasses, add ``-`` in summary between test name and reason, to match how xfail is displayed.

- `11825 &lt;https://github.com/pytest-dev/pytest/issues/11825&gt;`_: The :hook:`pytest_plugin_registered` hook has a new ``plugin_name`` parameter containing the name by which ``plugin`` is registered.


Bug Fixes
---------

- `11706 &lt;https://github.com/pytest-dev/pytest/issues/11706&gt;`_: Fix reporting of teardown errors in higher-scoped fixtures when using `--maxfail` or `--stepwise`.


- `11758 &lt;https://github.com/pytest-dev/pytest/issues/11758&gt;`_: Fixed ``IndexError: string index out of range`` crash in ``if highlighted[-1] == &quot;\n&quot; and source[-1] != &quot;\n&quot;``.
This bug was introduced in pytest 8.0.0rc1.


- `9765 &lt;https://github.com/pytest-dev/pytest/issues/9765&gt;`_, `#11816 &lt;https://github.com/pytest-dev/pytest/issues/11816&gt;`_: Fixed a frustrating bug that afflicted some users with the only error being ``assert mod not in mods``. The issue was caused by the fact that ``str(Path(mod))`` and ``mod.__file__`` don&#x27;t necessarily produce the same string, and was being erroneously used interchangably in some places in the code.

This fix also broke the internal API of ``PytestPluginManager.consider_conftest`` by introducing a new parameter -- we mention this in case it is being used by external code, even if marked as *private*.

8.0.0rc1

============================

Breaking Changes
----------------

Old Deprecations Are Now Errors
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- `7363 &lt;https://github.com/pytest-dev/pytest/issues/7363&gt;`_: **PytestRemovedIn8Warning deprecation warnings are now errors by default.**

Following our plan to remove deprecated features with as little disruption as
possible, all warnings of type ``PytestRemovedIn8Warning`` now generate errors
instead of warning messages by default.

**The affected features will be effectively removed in pytest 8.1**, so please consult the
:ref:`deprecations` section in the docs for directions on how to update existing code.

In the pytest ``8.0.X`` series, it is possible to change the errors back into warnings as a
stopgap measure by adding this to your ``pytest.ini`` file:

.. code-block:: ini

   [pytest]
   filterwarnings =
       ignore::pytest.PytestRemovedIn8Warning

But this will stop working when pytest ``8.1`` is released.

**If you have concerns** about the removal of a specific feature, please add a
comment to :issue:`7363`.


Version Compatibility
^^^^^^^^^^^^^^^^^^^^^

- `11151 &lt;https://github.com/pytest-dev/pytest/issues/11151&gt;`_: Dropped support for Python 3.7, which `reached end-of-life on 2023-06-27 &lt;https://devguide.python.org/versions/&gt;`__.


- ``pluggy&gt;=1.3.0`` is now required.


Collection Changes
^^^^^^^^^^^^^^^^^^

In this version we&#x27;ve made several breaking changes to pytest&#x27;s collection phase,
particularly around how filesystem directories and Python packages are collected,
fixing deficiencies and allowing for cleanups and improvements to pytest&#x27;s internals.
A deprecation period for these changes was not possible.


- `7777 &lt;https://github.com/pytest-dev/pytest/issues/7777&gt;`_: Files and directories are now collected in alphabetical order jointly, unless changed by a plugin.
Previously, files were collected before directories.
See below for an example.


- `8976 &lt;https://github.com/pytest-dev/pytest/issues/8976&gt;`_: Running `pytest pkg/__init__.py` now collects the `pkg/__init__.py` file (module) only.
Previously, it collected the entire `pkg` package, including other test files in the directory, but excluding tests in the `__init__.py` file itself
(unless :confval:`python_files` was changed to allow `__init__.py` file).

To collect the entire package, specify just the directory: `pytest pkg`.


- `11137 &lt;https://github.com/pytest-dev/pytest/issues/11137&gt;`_: :class:`pytest.Package` is no longer a :class:`pytest.Module` or :class:`pytest.File`.

The ``Package`` collector node designates a Python package, that is, a directory with an `__init__.py` file.
Previously ``Package`` was a subtype of ``pytest.Module`` (which represents a single Python module),
the module being the `__init__.py` file.
This has been deemed a design mistake (see :issue:`11137` and :issue:`7777` for details).

The ``path`` property of ``Package`` nodes now points to the package directory instead of the ``__init__.py`` file.

Note that a ``Module`` node for ``__init__.py`` (which is not a ``Package``) may still exist,
if it is picked up during collection (e.g. if you configured :confval:`python_files` to include ``__init__.py`` files).


- `7777 &lt;https://github.com/pytest-dev/pytest/issues/7777&gt;`_: Added a new :class:`pytest.Directory` base collection node, which all collector nodes for filesystem directories are expected to subclass.
This is analogous to the existing :class:`pytest.File` for file nodes.

Changed :class:`pytest.Package` to be a subclass of :class:`pytest.Directory`.
A ``Package`` represents a filesystem directory which is a Python package,
i.e. contains an ``__init__.py`` file.

:class:`pytest.Package` now only collects files in its own directory; previously it collected recursively.
Sub-directories are collected as their own collector nodes, which then collect themselves, thus creating a collection tree which mirrors the filesystem hierarchy.

Added a new :class:`pytest.Dir` concrete collection node, a subclass of :class:`pytest.Directory`.
This node represents a filesystem directory, which is not a :class:`pytest.Package`,
that is, does not contain an ``__init__.py`` file.
Similarly to ``Package``, it only collects the files in its own directory.

:class:`pytest.Session` now only collects the initial arguments, without recursing into directories.
This work is now done by the :func:`recursive expansion process &lt;pytest.Collector.collect&gt;` of directory collector nodes.

:attr:`session.name &lt;pytest.Session.name&gt;` is now ``&quot;&quot;``; previously it was the rootdir directory name.
This matches :attr:`session.nodeid &lt;_pytest.nodes.Node.nodeid&gt;` which has always been `&quot;&quot;`.

The collection tree now contains directories/packages up to the :ref:`rootdir &lt;rootdir&gt;`,
for initial arguments that are found within the rootdir.
For files outside the rootdir, only the immediate directory/package is collected --
note however that collecting from outside the rootdir is discouraged.

As an example, given the following filesystem tree::

   myroot/
       pytest.ini
       top/
       ├── aaa
       │   └── test_aaa.py
       ├── test_a.py
       ├── test_b
       │   ├── __init__.py
       │   └── test_b.py
       ├── test_c.py
       └── zzz
           ├── __init__.py
           └── test_zzz.py

the collection tree, as shown by `pytest --collect-only top/` but with the otherwise-hidden :class:`~pytest.Session` node added for clarity,
is now the following::

   &lt;Session&gt;
     &lt;Dir myroot&gt;
       &lt;Dir top&gt;
         &lt;Dir aaa&gt;
           &lt;Module test_aaa.py&gt;
             &lt;Function test_it&gt;
         &lt;Module test_a.py&gt;
           &lt;Function test_it&gt;
         &lt;Package test_b&gt;
           &lt;Module test_b.py&gt;
             &lt;Function test_it&gt;
         &lt;Module test_c.py&gt;
           &lt;Function test_it&gt;
         &lt;Package zzz&gt;
           &lt;Module test_zzz.py&gt;
             &lt;Function test_it&gt;

Previously, it was::

   &lt;Session&gt;
     &lt;Module top/test_a.py&gt;
       &lt;Function test_it&gt;
     &lt;Module top/test_c.py&gt;
       &lt;Function test_it&gt;
     &lt;Module top/aaa/test_aaa.py&gt;
       &lt;Function test_it&gt;
     &lt;Package test_b&gt;
       &lt;Module test_b.py&gt;
         &lt;Function test_it&gt;
     &lt;Package zzz&gt;
       &lt;Module test_zzz.py&gt;
         &lt;Function test_it&gt;

Code/plugins which rely on a specific shape of the collection tree might need to update.


- `11676 &lt;https://github.com/pytest-dev/pytest/issues/11676&gt;`_: The classes :class:`~_pytest.nodes.Node`, :class:`~pytest.Collector`, :class:`~pytest.Item`, :class:`~pytest.File`, :class:`~_pytest.nodes.FSCollector` are now marked abstract (see :mod:`abc`).

We do not expect this change to affect users and plugin authors, it will only cause errors when the code is already wrong or problematic.


Other breaking changes
^^^^^^^^^^^^^^^^^^^^^^

These are breaking changes where deprecation was not possible.


- `11282 &lt;https://github.com/pytest-dev/pytest/issues/11282&gt;`_: Sanitized the handling of the ``default`` parameter when defining configuration options.

Previously if ``default`` was not supplied for :meth:`parser.addini &lt;pytest.Parser.addini&gt;` and the configuration option value was not defined in a test session, then calls to :func:`config.getini &lt;pytest.Config.getini&gt;` returned an *empty list* or an *empty string* depending on whether ``type`` was supplied or not respectively, which is clearly incorrect. Also, ``None`` was not honored even if ``default=None`` was used explicitly while defining the option.

Now the behavior of :meth:`parser.addini &lt;pytest.Parser.addini&gt;` is as follows:

* If ``default`` is NOT passed but ``type`` is provided, then a type-specific default will be returned. For example ``type=bool`` will return ``False``, ``type=str`` will return ``&quot;&quot;``, etc.
* If ``default=None`` is passed and the option is not defined in a test session, then ``None`` will be returned, regardless of the ``type``.
* If neither ``default`` nor ``type`` are provided, assume ``type=str`` and return ``&quot;&quot;`` as default (this is as per previous behavior).

The team decided to not introduce a deprecation period for this change, as doing so would be complicated both in terms of communicating this to the community as well as implementing it, and also because the team believes this change should not break existing plugins except in rare cases.


- `11667 &lt;https://github.com/pytest-dev/pytest/issues/11667&gt;`_: pytest&#x27;s ``setup.py`` file is removed.
If you relied on this file, e.g. to install pytest using ``setup.py install``,
please see `Why you shouldn&#x27;t invoke setup.py directly &lt;https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary&gt;`_ for alternatives.


- `9288 &lt;https://github.com/pytest-dev/pytest/issues/9288&gt;`_: :func:`~pytest.warns` now re-emits unmatched warnings when the context
closes -- previously it would consume all warnings, hiding those that were not
matched by the function.

While this is a new feature, we announce it as a breaking change
because many test suites are configured to error-out on warnings, and will
therefore fail on the newly-re-emitted warnings.



Deprecations
------------

- `10465 &lt;https://github.com/pytest-dev/pytest/issues/10465&gt;`_: Test functions returning a value other than ``None`` will now issue a :class:`pytest.PytestWarning` instead of ``pytest.PytestRemovedIn8Warning``, meaning this will stay a warning instead of becoming an error in the future.


- `3664 &lt;https://github.com/pytest-dev/pytest/issues/3664&gt;`_: Applying a mark to a fixture function now issues a warning: marks in fixtures never had any effect, but it is a common user error to apply a mark to a fixture (for example ``usefixtures``) and expect it to work.

This will become an error in pytest 9.0.



Features and Improvements
-------------------------

Improved Diffs
^^^^^^^^^^^^^^

These changes improve the diffs that pytest prints when an assertion fails.
Note that syntax highlighting requires the ``pygments`` package.


- `11520 &lt;https://github.com/pytest-dev/pytest/issues/11520&gt;`_: The very verbose (``-vv``) diff output is now colored as a diff instead of a big chunk of red.

Python code in error reports is now syntax-highlighted as Python.

The sections in the error reports are now better separated.


- `1531 &lt;https://github.com/pytest-dev/pytest/issues/1531&gt;`_: The very verbose diff (``-vv``) for every standard library container type is improved. The indentation is now consistent and the markers are on their own separate lines, which should reduce the diffs shown to users.

Previously, the standard Python pretty printer was used to generate the output, which puts opening and closing
markers on the same line as the first/last entry, in addition to not having consistent indentation.


- `10617 &lt;https://github.com/pytest-dev/pytest/issues/10617&gt;`_: Added more comprehensive set assertion rewrites for comparisons other than equality ``==``, with
the following operations now providing better failure messages: ``!=``, ``&lt;=``, ``&gt;=``, ``&lt;``, and ``&gt;``.


Separate Control For Assertion Verbosity
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- `11387 &lt;https://github.com/pytest-dev/pytest/issues/11387&gt;`_: Added the new :confval:`verbosity_assertions` configuration option for fine-grained control of failed assertions verbosity.

If you&#x27;ve ever wished that pytest always show you full diffs, but without making everything else verbose, this is for you.

See :ref:`Fine-grained verbosity &lt;pytest.fine_grained_verbosity&gt;` for more details.

For plugin authors, :attr:`config.get_verbosity &lt;pytest.Config.get_verbosity&gt;` can be used to retrieve the verbosity level for a specific verbosity type.


Additional Support For Exception Groups and ``__notes__``
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

These changes improve pytest&#x27;s support for exception groups.


- `10441 &lt;https://github.com/pytest-dev/pytest/issues/10441&gt;`_: Added :func:`ExceptionInfo.group_contains() &lt;pytest.ExceptionInfo.group_contains&gt;`, an assertion helper that tests if an :class:`ExceptionGroup` contains a matching exception.

See :ref:`assert-matching-exception-groups` for an example.


- `11227 &lt;https://github.com/pytest-dev/pytest/issues/11227&gt;`_: Allow :func:`pytest.raises` ``match`` argument to match against `PEP-678 &lt;https://peps.python.org/pep-0678/&gt;` ``__notes__``.


Custom Directory collectors
^^^^^^^^^^^^^^^^^^^^^^^^^^^

- `7777 &lt;https://github.com/pytest-dev/pytest/issues/7777&gt;`_: Added a new hook :hook:`pytest_collect_directory`,
which is called by filesystem-traversing collector nodes,
such as :class:`pytest.Session`, :class:`pytest.Dir` and :class:`pytest.Package`,
to create a collector node for a sub-directory.
It is expected to return a subclass of :class:`pytest.Directory`.
This hook allows plugins to :ref:`customize the collection of directories &lt;custom directory collectors&gt;`.


&quot;New-style&quot; Hook Wrappers
^^^^^^^^^^^^^^^^^^^^^^^^^

- `11122 &lt;https://github.com/pytest-dev/pytest/issues/11122&gt;`_: pytest now uses &quot;new-style&quot; hook wrappers internally, available since pluggy 1.2.0.
See `pluggy&#x27;s 1.2.0 changelog &lt;https://pluggy.readthedocs.io/en/latest/changelog.html#pluggy-1-2-0-2023-06-21&gt;`_ and the :ref:`updated docs &lt;hookwrapper&gt;` for details.

Plugins which want to use new-style wrappers can do so if they require ``pytest&gt;=8``.


Other Improvements
^^^^^^^^^^^^^^^^^^

- `11216 &lt;https://github.com/pytest-dev/pytest/issues/11216&gt;`_: If a test is skipped from inside an :ref:`xunit setup fixture &lt;classic xunit&gt;`, the test summary now shows the test location instead of the fixture location.


- `11314 &lt;https://github.com/pytest-dev/pytest/issues/11314&gt;`_: Logging to a file using the ``--log-file`` option will use ``--log-level``, ``--log-format`` and ``--log-date-format`` as fallback
if ``--log-file-level``, ``--log-file-format`` and ``--log-file-date-format`` are not provided respectively.


- `11610 &lt;https://github.com/pytest-dev/pytest/issues/11610&gt;`_: Added the :func:`LogCaptureFixture.filtering() &lt;pytest.LogCaptureFixture.filtering&gt;` context manager which
adds a given :class:`logging.Filter` object to the :fixture:`caplog` fixture.


- `11447 &lt;https://github.com/pytest-dev/pytest/issues/11447&gt;`_: :func:`pytest.deprecated_call` now also considers warnings of type :class:`FutureWarning`.


- `11600 &lt;https://github.com/pytest-dev/pytest/issues/11600&gt;`_: Improved the documentation and type signature for :func:`pytest.mark.xfail &lt;pytest.mark.xfail&gt;`&#x27;s ``condition`` param to use ``False`` as the default value.


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: :class:`~pytest.FixtureDef` is now exported as ``pytest.FixtureDef`` for typing purposes.


- `11353 &lt;https://github.com/pytest-dev/pytest/issues/11353&gt;`_: Added typing to :class:`~pytest.PytestPluginManager`.


Bug Fixes
---------

- `10701 &lt;https://github.com/pytest-dev/pytest/issues/10701&gt;`_: :meth:`pytest.WarningsRecorder.pop` will return the most-closely-matched warning in the list,
rather than the first warning which is an instance of the requested type.


- `11255 &lt;https://github.com/pytest-dev/pytest/issues/11255&gt;`_: Fixed crash on `parametrize(..., scope=&quot;package&quot;)` without a package present.


- `11277 &lt;https://github.com/pytest-dev/pytest/issues/11277&gt;`_: Fixed a bug that when there are multiple fixtures for an indirect parameter,
the scope of the highest-scope fixture is picked for the parameter set, instead of that of the one with the narrowest scope.


- `11456 &lt;https://github.com/pytest-dev/pytest/issues/11456&gt;`_: Parametrized tests now *really do* ensure that the ids given to each input are unique - for
example, ``a, a, a0`` now results in ``a1, a2, a0`` instead of the previous (buggy) ``a0, a1, a0``.
This necessarily means changing nodeids where these were previously colliding, and for
readability adds an underscore when non-unique ids end in a number.


- `11563 &lt;https://github.com/pytest-dev/pytest/issues/11563&gt;`_: Fixed a crash when using an empty string for the same parametrized value more than once.


- `11712 &lt;https://github.com/pytest-dev/pytest/issues/11712&gt;`_: Fixed handling ``NO_COLOR`` and ``FORCE_COLOR`` to ignore an empty value.


- `9036 &lt;https://github.com/pytest-dev/pytest/issues/9036&gt;`_: ``pytest.warns`` and similar functions now capture warnings when an exception is raised inside a ``with`` block.



Improved Documentation
----------------------

- `11011 &lt;https://github.com/pytest-dev/pytest/issues/11011&gt;`_: Added a warning about modifying the root logger during tests when using ``caplog``.


- `11065 &lt;https://github.com/pytest-dev/pytest/issues/11065&gt;`_: Use ``pytestconfig`` instead of ``request.config`` in cache example to be consistent with the API documentation.


Trivial/Internal Changes
------------------------

- `11208 &lt;https://github.com/pytest-dev/pytest/issues/11208&gt;`_: The (internal) ``FixtureDef.cached_result`` type has changed.
Now the third item ``cached_result[2]``, when set, is an exception instance instead of an exception triplet.


- `11218 &lt;https://github.com/pytest-dev/pytest/issues/11218&gt;`_: (This entry is meant to assist plugins which access private pytest internals to instantiate ``FixtureRequest`` objects.)

:class:`~pytest.FixtureRequest` is now an abstract class which can&#x27;t be instantiated directly.
A new concrete ``TopRequest`` subclass of ``FixtureRequest`` has been added for the ``request`` fixture in test functions,
as counterpart to the existing ``SubRequest`` subclass for the ``request`` fixture in fixture functions.


- `11315 &lt;https://github.com/pytest-dev/pytest/issues/11315&gt;`_: The :fixture:`pytester` fixture now uses the :fixture:`monkeypatch` fixture to manage the current working directory.
If you use ``pytester`` in combination with :func:`monkeypatch.undo() &lt;pytest.MonkeyPatch.undo&gt;`, the CWD might get restored.
Use :func:`monkeypatch.context() &lt;pytest.MonkeyPatch.context&gt;` instead.


- `11333 &lt;https://github.com/pytest-dev/pytest/issues/11333&gt;`_: Corrected the spelling of ``Config.ArgsSource.INVOCATION_DIR``.
The previous spelling ``INCOVATION_DIR`` remains as an alias.


- `11638 &lt;https://github.com/pytest-dev/pytest/issues/11638&gt;`_: Fixed the selftests to pass correctly if ``FORCE_COLOR``, ``NO_COLOR`` or ``PY_COLORS`` is set in the calling environment.

7.4.4

=========================

Bug Fixes
---------

- `11140 &lt;https://github.com/pytest-dev/pytest/issues/11140&gt;`_: Fix non-string constants at the top of file being detected as docstrings on Python&gt;=3.8.


- `11572 &lt;https://github.com/pytest-dev/pytest/issues/11572&gt;`_: Handle an edge case where :data:`sys.stderr` and :data:`sys.__stderr__` might already be closed when :ref:`faulthandler` is tearing down.


- `11710 &lt;https://github.com/pytest-dev/pyt

pyup-bot · 2024-03-01T19:03:13Z

Closing this in favor of #239

pyup-bot added 13 commits February 1, 2024 20:03

Update coverage from 6.3.2 to 7.4.1

b7097d2

Update flake8 from 4.0.1 to 7.0.0

10d710c

Update pre-commit from 2.17.0 to 3.6.0

0edabe1

Update pytest from 7.0.1 to 8.0.0

8ce5fc0

Update pytest-mock from 3.7.0 to 3.12.0

fe06a0b

Update requests-mock from 1.9.3 to 1.11.0

bb63371

Update sphinx from 4.4.0 to 7.2.6

f850b1c

Update sphinx-markdown-tables from 0.0.15 to 0.0.17

c452b11

Update sphinx-rtd-theme from 1.0.0 to 2.0.0

a1735e3

Update click from 8.0.4 to 8.1.7

7c64d2c

Update gitpython from 3.1.27 to 3.1.41

15439b6

Update requests from 2.27.1 to 2.31.0

ec27949

Update tabulate from 0.8.9 to 0.9.0

738d9e1

pyup-bot added the update label Feb 1, 2024

pyup-bot mentioned this pull request Feb 1, 2024

Scheduled monthly dependency update for January #237

Closed

pyup-bot closed this Mar 1, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Scheduled monthly dependency update for February #238

Scheduled monthly dependency update for February #238

pyup-bot commented Feb 1, 2024

pyup-bot commented Mar 1, 2024

Scheduled monthly dependency update for February #238

Scheduled monthly dependency update for February #238

Conversation

pyup-bot commented Feb 1, 2024

Update coverage from 6.3.2 to 7.4.1.

7.4.1

7.4.0

7.3.4

7.3.3

7.3.2

7.3.1

7.3.0

7.2.7

7.2.6

7.2.5

7.2.4

7.2.3

7.2.2

7.2.1

7.2.0

7.1.0

7.0.5

7.0.4

7.0.3

7.0.2

7.0.1

7.0.0

7.0.0b1

6.6.0b1

6.5.0

6.4.4

6.4.3

6.4.2

6.4.1

6.4

6.3.3

Update flake8 from 4.0.1 to 7.0.0.

Update pre-commit from 2.17.0 to 3.6.0.

3.6.0

3.5.0

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

3.2.2

3.2.1

3.2.0

3.1.1

3.1.0

3.0.4

3.0.3

3.0.2

3.0.1

3.0.0

2.21.0

2.20.0

2.19.0

2.18.1

2.18.0

Update pytest from 7.0.1 to 8.0.0.

8.0.0

8.0.0rc2

8.0.0rc1

7.4.4

pyup-bot commented Mar 1, 2024