[renovate]

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	>=7.13.5 → >=7.17.0
mypy (changelog)	>=2.3.1 → >=2.4.0
pytest (changelog)	>=9.0.3 → >=9.2.0
tox (changelog)	>=4.22 → >=4.66.0
tox-uv (changelog)	>=1.35.2 → >=1.37.2
types-requests (changelog)	>=2.33.0.20260906 → >=2.33.0.20261006

---

Release Notes

coveragepy/coveragepy (coverage)

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:

v7.16.2

Compare Source

• Fix: on Python 3.14 and later, a for loop completing immediately before a
  function return could mistakenly report an uncovered branch. This is now
  fixed, closing issue 2168_.

• Fix: on Python 3.14 and later, the else clause of a try whose body is
  a with statement could incorrectly be reported as covered when the
  with raised. This is now fixed, closing issue 2289_.

• Fix: with dynamic_context = test_function, test methods written as
  @staticmethod or @classmethod were not given a context of their own.
  Now they are, on Python 3.11 and later. Closes issue 1923_.

.. _issue 1923: #​1923
.. _issue 2168: #​2168
.. _issue 2289: #​2289

.. _changes_7-16-1:

v7.16.1

Compare Source

• Fix: when the body of an irrefutable case (like case _:) is entirely
  excluded, the case line is now excluded too, just as an excluded
  else: body removes the else: line. Previously the case line was
  left behind and reported as missing. Closes issue 1563_ with pull 2269_.

• Fix: using :meth:.CoverageData.update twice on an in-memory database would
  fail, as described in issue 2279_. This is now fixed.

• Fix: the Total row in the footer of the HTML report's index page was
  recomputed in JavaScript with rounding that could disagree with the total
  the server rendered in the heading, including showing 100% when coverage
  was not complete. The footer now clamps values the way the rest of the
  report does, and when nothing is filtered out it is shown exactly as the
  server rendered it, so the two can't disagree. That also keeps rows the
  report omits (--skip-covered drops fully covered files) in the total.
  Fixes issue 2256_.

.. _issue 1563: #​1563
.. _issue 2256: #​2256
.. _pull 2269: #​2269
.. _issue 2279: #​2279

.. _changes_7-16-0:

v7.16.0

Compare Source

• When combining files, now path separator slashes will automatically be
  converted to the local file system style. This makes it less necessary to
  define [paths] configuration to combine data across operating systems.
  Fixes issue 2266_.

• The :meth:.Coverage.switch_context method now returns the previous context.

• Fix: previously, a [paths] pattern would be replaced everywhere in a file
  path when it was only meant to be replaced once, in the leading portion of
  the path. This is now fixed, in pull 2268_.

• Fixes to validation of options and configuration settings:

  • Negative precision settings now always cause useful error messages (pull 2261_).

  • An invalid regex in the --contexts option (or the [report] contexts setting) reported a confusing "Couldn't use data file ...:
    user-defined function raised exception" error. Now it raises a proper
    configuration error naming the bad regex, like other regex settings do
    (pull 2262_).

  • Non-string values in TOML configuration settings now produce a helpful
    error message instead of a traceback. This affects list settings whose
    elements aren't strings (like omit, exclude_lines, or a [paths]
    entry), file settings like data_file, and any wrong-typed value in the
    [paths] section (pull 2263_).

  • coverage run refuses run-affecting command-line options like
    --branch alongside --concurrency=multiprocessing, since they can't
    reach the subprocesses. The check only recognized multiprocessing as
    the entire option value, so --concurrency=multiprocessing,thread
    slipped through and failed later with "Can't combine statement coverage
    data with branch data". Each named concurrency library is now properly
    considered (pull 2270_).

• Fix: coverage annotate -d DIR raised an AssertionError if any
  measured file had an extension other than .py, such as a .pyw file on
  Windows. The original extension is now restored on the annotated copy (pull 2265_).

.. _pull 2261: #​2261
.. _pull 2262: #​2262
.. _pull 2263: #​2263
.. _pull 2265: #​2265
.. _issue 2266: #​2266
.. _pull 2268: #​2268
.. _pull 2270: #​2270

.. _changes_7-15-4:

v7.15.4

Compare Source

• Fix: in the HTML report, a source file name containing a double quote (legal
  on POSIX) wasn't escaped where it's dropped into the href of the index
  and prev/next links, so it could close the attribute early and inject markup.
  Page URLs are now escaped. Thanks, Rajath Mohare <pull 2227_>_.

• Fix: the LCOV report wrote file names and other fields into its
  line-oriented records without neutralizing control characters. A measured
  file whose name contained a newline (legal on POSIX) could forge extra
  records, inflating the coverage seen by tools that read the report. Control
  characters in a field are now replaced. Thanks, Rajath Mohare <pull 2226_>_.

• Wheels are now provided for Python 3.15.

.. _pull 2226: #​2226
.. _pull 2227: #​2227

.. _changes_7-15-3:

v7.15.3

Compare Source

• Fix: the sysmon core is incompatible with dynamic contexts. Previously, the
  combination would be prevented when read from the coverage.py configuration.
  But using the context API as pytest-cov does, contexts would be silently
  dropped. Now a warning is issued, thanks to Jisang Han <pull 2234_>.
  Closes issue 2200.

• A performance improvement in the low-level line number bookkeeping when
  combining data files, thanks to Kevin Turcios <pull 2239_>_.

• Performance improvement in HTML reporting by reducing the number of times
  files have to be parsed, thanks to Kevin Turcios <pull 2240_>_.

.. _issue 2200: #​2200
.. _pull 2234: #​2234
.. _pull 2239: #​2239
.. _pull 2240: #​2240

.. _changes_7-15-2:

v7.15.2

Compare Source

• Fix: one of the performance improvements in 7.15.1 (pull 2215) dramatically
  increased memory use during reporting for large projects. Now we use a
  different approach that is both faster and slimmer than 7.15.0. Fixes issue 2229_.

.. _issue 2229: #​2229

.. _changes_7-15-1:

v7.15.1

Compare Source

• Fix: in the HTML report with show_contexts enabled, a context label
  containing </script> (for example a parametrized pytest node id) could
  close the inline <script> element in a file page early, injecting markup.
  Context labels are now fully escaped. Thanks, Rajath Mohare <pull 2224_>_.

• A number of performance improvements thanks to Paul Kehrer, in pull requests
  2213 <pull 2213_>, 2214 <pull 2214_>, 2215 <pull 2215_>, 2216 <pull 2216_>, 2218 <pull 2218_>, 2220 <pull 2220_>, and 2221 <pull 2221_>_.

.. _pull 2213: #​2213
.. _pull 2214: #​2214
.. _pull 2215: #​2215
.. _pull 2216: #​2216
.. _pull 2218: #​2218
.. _pull 2220: #​2220
.. _pull 2221: #​2221
.. _pull 2224: #​2224

.. _changes_7-15-0:

v7.15.0

Compare Source

• Since 7.14.0, reporting commands implicitly combine parallel data files. Now
  those commands have a new option --keep-combined to retain the data files
  after combining them instead of the default, which is to delete them.
  Finishes issue 2198_.

• Fix: the LCOV report would incorrectly count excluded functions as uncovered,
  as described in issue 2205. This is now fixed thanks to Martin Kuntz Jacobsen <pull 2206_>.

• When running your program, coverage now correctly sets
  yourmodule.__spec__.loader as strongly recommended <--loader--_>,
  avoiding the deprecation warning described in issue 2208. Thanks, A5rocks <pull 2209_>_.

• Fix: with Python 3.10, running with the -I (isolated mode) option didn't
  correctly omit the current directory from the module search path, as
  described in issue 2103. That is now fixed thanks to Ilia Sorokin <pull 2211_>.

.. --loader--: https://docs.python.org/3/reference/datamodel.html#module.__loader_
.. _issue 2103: #​2103
.. _issue 2198: #​2198
.. _issue 2205: #​2205
.. _pull 2206: #​2206
.. _issue 2208: #​2208
.. _pull 2209: #​2209
.. _pull 2211: #​2211

.. _changes_7-14-3:

v7.14.3

Compare Source

• Fix: the default ... exclusion rule now also matches function bodies
  whose closing return-type bracket is on its own line (for example, after a
  long -> dict[ ... ] annotation that a formatter has split over multiple
  lines). Closes issue 2185, thanks Mengjia Shang <pull 2196_>.

• Fix: On 3.13t, we incorrectly issued Couldn't import C tracer errors.
  We can't import the C tracer because in 7.14.2 we stopped shipping compiled
  wheels for 3.13t. Thanks, Hugo van Kemenade <pull 2203_>_.

.. _issue 2185: #​2185
.. _pull 2196: #​2196
.. _pull 2203: #​2203

.. _changes_7-14-2:

v7.14.2

Compare Source

• Fix: some messages were being written to stdout, making coverage json -o - useless for capturing JSON output. Now messages are written to stderr,
  fixing issue 2197_.

• Fix: CoverageData kept one SQLite connection per thread that recorded
  coverage, but never closed them when those threads terminated. On long runs
  with many short-lived threads this leaked one file descriptor per dead
  thread, eventually failing with OSError: [Errno 24] Too many open files.
  Connections belonging to terminated threads are now closed and dropped.
  Fixes issue 2192. Thanks, Matthew Lloyd <pull 2193_>.

• Fix: when using sys.monitoring, we were assuming we could use the
  COVERAGE_ID tool id. But other tools might also assume they could use
  that id. Pre-allocated ids don't really make sense, so now we search for a
  usable one instead. Fixes issue 2187_.

• Following the advice of cibuildwheel <no-13t_>_, we no longer distribute
  wheels for Python 3.13 free-threaded.

.. _issue 2187: #​2187
.. _issue 2192: #​2192
.. _pull 2193: #​2193
.. _issue 2197: #​2197
.. _no-13t: https://py-free-threading.github.io/ci/#building-free-threaded-wheels-with-cibuildwheel

.. _changes_7-14-1:

v7.14.1

Compare Source

• Fix: the HTML report used typographic niceties to make file paths more
  readable by adding a small amount of space around slashes. Those spaces
  interfered with searching the page for file paths of interest. Now the report
  uses CSS to accomplish the same visual tweak so that searches with slashes
  work correctly. Closes issue 2170_.

• Add a 3.16 PyPI classifier <hugo-316_>_ since we test on the 3.16 main
  branch.

.. _issue 2170: #​2170
.. _hugo-316: https://mastodon.social/@hugovk/116588523571204490

.. _changes_7-14-0:

v7.14.0

Compare Source

• Feature: now when running one of the reporting commands, if there are
  parallel data files that need combining, they will be implicitly combined
  before creating the report. There is no option to avoid the combination; let
  us know if you have a use case that requires it. Thanks, Tim Hatch <pull 2162_>. Closes issue 1781.

• Fix: the output from combine was too verbose, listing each file
  considered. Now it shows a single line with the counts of files combined,
  files skipped, and files with errors. The -q flag suppresses this line.
  The old detailed lines are available with the new --debug=combine option.

• Fix: running a Python file through a symlink now sets the sys.path correctly,
  matching regular Python behavior. Fixes issue 2157_.

• Fix: Collector.flush_data could fail with "RuntimeError: Set changed
  size during iteration" when a tracer in another thread added a line to the
  per-file set that add_lines (or add_arcs) was iterating. The values
  passed to CoverageData are now snapshotted via dict.copy() and
  set.copy(), which are atomic under the GIL. Thanks, Alex Vandiver <pull 2165_>_.

• Fix: the soft keyword lazy is now bolded in HTML reports.

• We are no longer testing eventlet support. Eventlet started issuing stern
  deprecation warnings that break our tests. Our support code is still there.

.. _issue 1781: #​1781
.. _issue 2157: #​2157
.. _pull 2162: #​2162
.. _pull 2165: #​2165

.. _changes_7-13-5:

python/mypy (mypy)

v2.4.0

Compare Source

pytest-dev/pytest (pytest)

v9.2.0

Compare Source

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

• #​14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

• #​8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

  Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

• #​993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

  • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
  • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

  pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

• #​14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec.
  The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

• #​14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

• #​14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1,
  all higher-scoped fixtures (module, package, and session) defined
  as instance methods are now deprecated.

  They suffer from the same issue the original deprecation only fixed for
  class-scoped fixtures, see 10819 and 14011.

• #​14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

• #​7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

• #​14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
• #​2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
• #​6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

• #​10745: A RecursionError whose recursion origin cannot be located now shows only the
  first and last 10 stack frames, matching what pytest already did when locating
  the origin failed outright. Previously the full traceback -- often around a
  thousand near-identical frames -- was rendered, which was both slow and
  unreadable. Pass --full-trace to see every frame.

• #​10745: The line numbers of a module's statements are now computed once per traceback
  instead of once per traceback entry, which noticeably speeds up rendering
  failures raised from large test modules.

• #​11418: The cached rewritten modules in __pycache__ are now invalidated by a hash of
  the source instead of its modification time, using the checked-hash pyc format
  from 552.

  Timestamps make the cache useless wherever source files get fresh modification
  times, most notably in CI: a checkout gives every file a new mtime, so a
  restored cache is discarded in full and every test module is rewritten again.
  Hashing the source costs roughly 15 microseconds per file and makes the cache
  survive that.

  Existing timestamp based caches are ignored and rewritten once.

• #​12624: The pytest_plugins variable and the PYTEST_PLUGINS environment variable now also accept entry point names of installed plugins (e.g. xdist), in addition to importable module names, matching the behavior of the -p command-line option.

  As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the plugins: line of the terminal header (12615).

  Based on the original implementation by Marcel Telka in 12616.

• #​12697: Warnings emitted while importing plugins through -p, PYTEST_PLUGINS, or entry point autoloading are now captured, filtered, and reported like other warnings.

• #​12860: Assertion diffs for dict.items() and dict.keys() comparisons (>=, <=, >, <, ==) now show which items are missing, the same way set comparisons do.

• #​13354: Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> now also accepts a ~pytest.MarkDecorator as its default, for example item.get_closest_marker("foo", pytest.mark.foo(1)), and returns the wrapped ~pytest.Mark.

  Previously the only way to build a default was to instantiate ~pytest.Mark directly, which is private and warns.

• #​13369: Improved the error from pytest.RunResult.assert_outcomes when a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins.

• #​13431: Exposed pytest.ParameterSet as the type of the return value of pytest.param().
  This can be used in type annotations and isinstance checks.

• #​13564: Issue a warning when fixtures are wrapped with a decorator that prevents
  correct discovery, including @classmethod above @pytest.fixture and
  @staticmethod above @pytest.fixture. Put @pytest.fixture above
  those decorators on test classes.

• #​14164: Exposed pytest.Approx as the type of the return value of pytest.approx().
  This can be used in type annotations and isinstance checks.

• #​14463: Assertion diffs for mappings now match up keys the way the compared mappings match them themselves.

  Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping
  with its own notion of key equivalence, such as case-insensitive header mappings, no longer
  reports its common keys as missing on either side.

• #​14523: Large assertion comparison diffs are now built lazily and capped to the
  truncation budget, so a huge diff is no longer formatted in full just to
  be truncated. As a consequence, the truncation footer no longer
  reports the exact number of hidden lines.

• #​14687: The default fd-level output capturing (--capture=fd) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites.

• #​14724: --no-summary now only applies directly to pytest's own summary.

  The flag no longer skips the pytest_terminal_summary hook, so third-party
  plugins (for example coverage) can still write their terminal summaries.

• #​14751: parser.addini <pytest.Parser.addini> now also accepts type expressions for its type argument, in addition to the existing string tags: the plain Python types str, bool, int, float, a Literal of strings, and unions of these (for example int | str or int | Literal["auto"]).

• #​14754: pytest.approx() now rejects infinite relative tolerances for datetime.timedelta values with a clear ValueError instead of raising OverflowError.

• #​14791: The junit_family, junit_logging, junit_duration_report, console_output_style, empty_parameter_set_mark, assertion_text_diff_style and tmp_path_retention_policy configuration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, and pytest --help lists the accepted values.

  config.getini <pytest.Config.getini> now raises pytest.UsageError instead of TypeError or ValueError when the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raises ValueError.

• #​15006: pytest.approx now emits pytest.PytestApproxDecimalToleranceWarning when a rel or abs tolerance is given as a float that cannot be represented exactly for a ~decimal.Decimal comparison, since such a tolerance is widened to the float's exact binary value.

• #​14675, #​14953, #​15153, #​15132: The truncation_limit_lines, truncation_limit_chars, max_warnings, verbosity_assertions, verbosity_test_cases, verbosity_subtests, tmp_path_retention_count, log_level, log_cli_level, log_file_level,log_auto_indent and faulthandler_timeout configuration options now accept native integer (and, for log_auto_indent, boolean) values in TOML configuration files, while still accepting strings for backward compatibility.
  log_file_mode now reports invalid values as a usage error.

• #​15254: tmp_path and TempPathFactory.mktemp <pytest.TempPathFactory.mktemp> no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist.

• #​4569: Node.add_marker <_pytest.nodes.Node.add_marker> now stores a ~pytest.Mark in node.keywords, matching what marks applied during collection store. Previously it stored a ~pytest.MarkDecorator.

• #​9436: Avoided formatting tracebacks for tests marked with xfail(run=False).

Bug fixes

• #​10128: Configured warning filters now apply to warnings emitted by pytest_configure hooks.

• #​10210: pytest.approx now raises a TypeError for any nested container, not
  only for one of the same type as its parent. Previously approx([{"k": 1}])
  and approx({"k": [1]}) were accepted and then compared unequal to every
  value, silently ignoring the tolerance, while approx([[1]]) correctly
  reported that nesting is unsupported.

• #​10644: monkeypatch.setattr() no longer leaves a new entry in the instance __dict__ when it patches an attribute that the instance inherits from its class.

  Previously undo() assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically.

• #​1139: Fixed tracebacks showing ??? instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root.
  The source lookup now falls back to searching sys.path for such filenames, as the standard traceback module does.

• #​11502: The rootdir is no longer derived from a configuration file that is not a regular file, such as --config-file=/dev/null.

• #​11783: Plugins installed in editable mode (660) are marked for assertion rewriting again.

  Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case.

• #​11933: pytest.warns no longer re-emits unmatched warnings with module="warnings", which caused module-based warning filters to be applied to the wrong warnings. Since warnings.WarningMessage does not record the module a warning was emitted with, re-emitted warnings now use the standard warnings.warn_explicit default of deriving the module from the warning's filename.

• #​12175: ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly> now strips the AssertionError: prefix of failed assert statements for ~pytest.ExceptionInfo objects created by pytest.raises, and failures inside unittest.TestCase.subTest report the same short crash line as regular tests.

• #​12223: The message attribute of <failure> and <error> elements in --junitxml reports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with -vv) produced attributes tens of thousands of characters long, which some XML parsers fail on.

• #​12307: Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in assert condition, msg) when using -vv: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with ....

• #​12824: Custom command-line options now fail with a clear error when their implicit
  destination conflicts with an existing option, avoiding silent overrides of
  built-in options such as -k.

• #​13292: Fixed a stale rewritten module being used when a test file is modified twice
  within the same second without changing its size -- the pyc header could only
  record whole-second timestamps. The cache is now keyed on a hash of the source.

• #​14036: __tracebackhide__ is now respected in ExceptionGroup tracebacks, both for the group itself and for its sub-exceptions.

• #​14189: Nested usage of caplog.filtering <pytest.LogCaptureFixture.filtering> no longer removes filters early if they were already present.

• #​14412: Fixed incorrect timing information for subtests and parent tests when console_output_style = "times".

• #​14445: Assertion rewriting no longer evaluates walrus operator (:=) expressions more than once, which reported results the test never computed when the expression had side effects.

  An operand evaluated before a later walrus is now reported with the value it actually saw, so assert value != identity(value := value.lower()) keeps Python's left-to-right order.

• #​14552: Fixed stale co_filename values after a test module or directory is moved. Assertion-rewrite caches are reused when the source hash still matches, and in-memory code objects are pointed at the current path.

• #​14586: Negative values passed to log_auto_indent now correctly fall back to no indentation, matching the documented behavior.

• #​14619: Fixed a crash in pytest.mark.parametrize when a non-sequence value is passed for a parameter set. It now provides a clear error message during collection.

• #​14635: Fixed fixture resolution failures when specifying multiple test paths on the command line that share common parent directories. Parametrized fixtures defined in a conftest.py could be silently dropped depending on the order of the specified paths.

• #​14637: Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning.

• #​14638: Top-level options in pytest.toml and .pytest.toml files now raise an error instead of being silently ignored when no [pytest] table is present.

• #​14683: Fixed a regression in pytest 9.1 where a conftest.py located in the rootdir was no longer visible to tests and doctests collected from outside the rootdir (for example when passing a parent directory of the rootdir as a collection argument, or setting --rootdir to a subdirectory).

  As a result, fixtures defined in such a conftest -- including doctest_namespace injections -- were not available, causing errors such as NameError in doctests.

• #​14700: Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped.

• #​14705: TOML configuration files passed via -c now also read their configuration from the [pytest] table, the one pytest's own configuration files use. The [tool.pytest] and [tool.pytest.ini_options] tables such files were previously restricted to keep working; using both styles in one file is an error.

• #​14828: Exception groups raised from another exception now print their cause chain only once in the traceback output.

• #​14864: Fixed collection on Windows collecting the whole suite instead of the given path, on file systems which do not support file IDs (st_ino is 0 for every file, as seen for example on sshfs-win/WinFsp mounts).

• #​14884: Cache.get(), Cache.set() and Cache.mkdir() now reject keys that resolve outside the cache directory, and --cache-show ignores glob matches outside it.

• #​14909: Fixed MonkeyPatch.delattr <pytest.MonkeyPatch.delattr>, MonkeyPatch.setitem <pytest.MonkeyPatch.setitem> and MonkeyPatch.delitem <pytest.MonkeyPatch.delitem> recording a stale undo entry when the underlying mutation failed, which could cause spurious errors during teardown. The undo entry is now recorded only after the mutation succeeds, matching the behavior of MonkeyPatch.setattr <pytest.MonkeyPatch.setattr>.

• #​14912: ~pytest.PytestWarning instances defined in _pytest.deprecated are no longer reused across warnings.warn calls, so warnings raised as errors (e.g. with -W error) no longer accumulate stale traceback frames from previous raises.

• #​14942: Fixed a regression in 9.1.0 that made collection very slow (quadratic) when many fixtures are defined with the same name.
  This can happen particularly when many tests are defined in separate classes which inherit from a base class which defines fixtures (the fixtures are repeated per class).

• #​15005: pytest.approx no longer treats finite ~decimal.Decimal values outside the float range (such as Decimal("1e400")) as infinite, which made in-tolerance comparisons fail.

• #​15006: Restored the tolerance shown by pytest.approx for ~decimal.Decimal values, which since 9.0 displayed ??? for the default tolerance and reported the raw rel ratio instead of the absolute tolerance actually compared against.

• #​15006: The failure message for pytest.approx comparisons of ~decimal.Decimal collections no longer reports Max absolute difference: -inf, or crashes for mappings, when the decimal.FloatOperation trap is set.

• #​15006: pytest.approx no longer raises AttributeError when comparing numpy.ndarray instances with object dtype, such as arrays of ~decimal.Decimal.

• #​15032: Help texts for command-line options and configuration options now keep their indentation
  and blank lines. Previously each line was stripped before wrapping, so a wrapped
  list item was indistinguishable from a new one and blank lines were dropped; configuration
  option help lost its line breaks entirely.

• #​15043: Cache writes now emit pytest.PytestCacheWarning when writing or closing the cache file fails, consistent with errors opening the file.

• #​15052: Fixed possible off-by-one line numbers in --fixtures and --fixtures-per-test output.

• #​15145: With console_output_style set to times, durations just below a unit boundary are now shown in the next unit (e.g. 1.000ms instead of 1000.0us).

• #​15172: Assertion diffs now pretty-print the built-in frozendict (Python 3.15+) across multiple lines, similarly to how dict is displayed.

• #​4569: -k no longer matches attributes that end up in a test function's __dict__ without being meant as keywords, such as pytest's own pytestmark attribute and the bookkeeping left behind by functools.wraps and functools.lru_cache.

• #​6750: Fix fixture argument discovery for custom collectors that pass bound methods to pytest.Function.

• #​6997: XFAIL reports from teardown phases now include the phase in the short test
  summary.

• #​7940: Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed.

• #​8321: Fixed exception chains being duplicated in the traceback output when an exception in the chain (__cause__/__context__) has no traceback of its own, and that exception is itself linked to further exceptions.

• #​8914: Tests parametrized with higher-than-function scope are now reordered by
  parameter value rather than by parameter index, so that items using equal
  parameter values are grouped together and share a single fixture setup, even
  when they are parametrized by separate @pytest.mark.parametrize <pytest.mark.parametrize ref>
  calls. Previously, an expensive higher-scoped fixture could be set up and torn
  down repeatedly for the same parameter value.

  Unhashable parameter values (e.g. dicts) keep the previous index-based
  grouping behavior.

  As a consequence, the order in which parametrized tests run may change
  (fixture setup/teardown counts can only decrease, not increase).

• #​9924: Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure.

Improved documentation

• #​10721: Replaced setup.py usage with pyproject.toml in writing-plugins.
• #​12658: Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation.
• #​12857: Documented how --confcutdir affects initial conftest.py discovery.
• #​14157: Added the pytest-flakefighters plugin to the list of flaky test plugins in plugins.rst.
  Added flaky test papers published on the Test FLARE project to the list of flaky papers in plugins.rst.
• #​15127: Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type.
• #​15242: The installation instructions <installation> and install-package-with-pip now show how to install pytest into a virtual environment with venv and pip, uv or virtualenv, and explain the externally-managed-environment error.
• #​4569: pytest --help, the -k reference entry and select-tests no longer describe -k as a Python expression matched against test names only; keyword expressions now shows marker names being matched as well. The examples that looked up a marker use Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> rather than item.keywords.
• #​9614: Clarified that session.items and session.testscollected exclude deselected tests in the pytest_collection documentation.

Packaging updates and notes for downstreams

• #​11680: Source archives of arbitrary commits -- the tarballs GitHub serves under
  /archive/, not just the ones for tags -- can now be built into an sdist or a
  wheel with a correct version. A .git_archival.txt file, expanded by git archive via export-subst, carries the describe output that
  setuptools-scm would otherwise have to ask git for.

  The archival file deliberately omits ref-names. Recording it would make the
  content of an archive -- and therefore its checksum -- change whenever a branch
  that points at the archived commit is moved afterwards, which is how the
  equivalent tarballs of tagged releases became unstable for other projects.
  Describe output alone depends only on the commit and on the tags reachable from
  it.

  The archival file is not shipped in the sdist -- an sdist carries its version
  in its metadata, and the template is only ever expanded by git archive.

  Building pytest from a git checkout now requires setuptools-scm >= 10.1.

• #​9236: pluggy>=1.6 is now required.

  Older pluggy versions stopped running the remaining hook wrapper teardowns once an
  old-style hookwrapper raised in its own teardown. The logging plugin's wrapper was
  left suspended, and when it was finalised later it detached the handler that
  caplog of a subsequent test was recording through, so that test saw no records.

Contributor-facing changes

• #​14813: Added a systematic coverage matrix for assertion rewriting.
• #​14921: Added scripts/diff-assert-rewrite.py, which diffs the assert-rewritten form of a snippet between the plain source, this checkout and released pytest versions.
• #​15190: Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented DistFacade compatibility class.

Miscellaneous internal changes

• #​13888: FixtureRequest.node <pytest.FixtureRequest.node> is now explicitly annotated as returning Any, so strict pyright no lon

[!IMPORTANT]
✂ PR body was truncated to here.

---

Configuration

📅 Schedule: (in timezone Europe/Stockholm)

• Branch creation
  • Only on Monday (* * * * 1)
• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Using CPython 3.15.2 interpreter at: /opt/containerbase/tools/python/3.15.2/bin/python3
error: No solution found when resolving dependencies for split (markers: python_full_version == '3.10.*')
  cause: Because the requested Python version (>=3.10) does not satisfy Python>=3.11 and coverage==7.17.0 depends on Python>=3.11, we can conclude that coverage==7.17.0 cannot be used.
         And because only coverage<=7.17.0 is available, we can conclude that coverage>=7.17.0 cannot be used.
         And because phabfive:dev depends on coverage>=7.17.0 and your project requires phabfive:dev, we can conclude that your project's requirements are unsatisfiable.

hint: While the active Python version is 3.15, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using `requires-python`.

hint: The `requires-python` value (>=3.10) includes Python versions that are not supported by your dependencies (e.g., coverage==7.17.0 only supports >=3.11). Consider using a more restrictive `requires-python` value (like >=3.11).