test(rewrite): systematic coverage matrix for assertion rewriting by RonnyPfannschmidt · Pull Request #14813 · pytest-dev/pytest

RonnyPfannschmidt · 2026-07-31T19:01:24Z

The assertion rewriter is tested through its failure messages, one regression test per issue. That makes it hard to say whether a change improved anything: there is no place that records what the rewriter does and does not decompose.

This adds a matrix over expression types with four axes — introspection depth, semantic equivalence, single evaluation, and evaluation order.

The evaluation-order axis is new

Comparing pass/fail is not enough. An operand read after a later walrus operator rebound its name runs exactly once and can still fail the assertion, having compared the wrong value — so neither the semantic-equivalence axis nor the single-evaluation axis sees it.

assert_evaluation_order() compares what check() returns from a plain and a rewritten run. It cannot wrap the fragile operand to observe it: a bare name is exactly the case the rewriter leaves unhoisted, and putting a call around it would hoist it and hide the bug.

Most operands are safe today because generic_visit hoists them into a temporary. The passing tests in that class are guards, and they are the point: they keep that true as new visitors take expression types away from generic_visit.

Only what passes

Per review, this PR carries no xfails — every test here passes on main, and there is nothing to assess the merits of before merging.

The gaps the matrix originally recorded as xfails have moved onto the PRs that close them, so each lands green alongside the fix that makes it green:


#14447	walrus single evaluation and operand order (+10)
#14814	raw walrus and starred operands (+2)
#14815	`visit_Subscript` (+3)
#14816	`visit_IfExp` (+3)
#14817	flat method-call display (+6)
#14821	operands rebound by a call — #14820 (+3)
#14822	lazy chained comparisons — #14819 (+2)
#14916	the two gaps nothing in this series fixes, as strict xfails

71 tests here, 100 by the end of the series.

No behaviour change

This PR only describes the rewriter; the fixes are the PRs above.

The rewriter is tested through its failure messages, one regression test per issue. That makes it hard to say whether a change improved anything: there is no place that records what the rewriter cannot do yet. Add a matrix over expression types with four axes -- introspection depth, semantic equivalence, single evaluation, and evaluation order -- and record every known gap as a strict xfail tagged with a group name. A change that closes one names the group and flips its markers; strictness means it cannot forget. The evaluation-order axis is new. Comparing pass/fail is not enough: an operand read after a later walrus operator rebound its name runs exactly once and can still fail the assertion, having compared the wrong value. assert_evaluation_order() compares what check() returns, because the fragile operand is a bare name -- wrapping it in a call to observe it would hoist it and hide the bug. Behaviour is unchanged; this only describes it.

bluetech

Seems like a good initiative!

A few comments:

As I write in one of the comments, I think some of the xfails are not entirely appropriate in this PR. e.g. the introspection xfails are mostly for possible enhancements, not strictly bugs, and we don't usually use xfails for those, I think for a good reason. I suggest leaving those out for now and adding them when the corresponding feature is actually implemented.
The def check() is a bit noisy, I wonder if the assert functions can't handle it themselves, and the tests themselves just give the straight code? I know there's a local/global distinction and a couple of tests that explicitly care about that, but if we can make the common case shorter I think it would be nice.
I wonder why not run all checks on all examples, instead of picking specific asserts for specific examples? Why not have the full coverage?
Obviously these are a lot of new tests, I wonder if there are some existing tests that are subsumed by this and could be removed? Just to keep things manageable.

RonnyPfannschmidt · 2026-08-20T04:50:03Z

wrt the main questions

xfail moved as suggested

def check() — the sources are indented into the calls now, which covers most of it. Auto-wrapping only helps the introspection tests: TestEvaluationOrder needs check() to carry a try/except and return its observations either way, and one shape beats two.

All checks on all examples — introspection needs a hand-written must_contain, and evaluation order needs the example to contain a rebinding and return what it saw, so neither generalises to arbitrary examples. Semantic equivalence and passes-when-true do.

Subsumed tests — TestAssertionRewriteWalrusOperator is 14 runpytest() tests the matrix now covers in-process. test_assertion_walrus_operator even passes straight through the ordering bug the matrix catches, since it only checks ret == 0. I'd delete them in #14447 next to the fix rather than on a test-only PR.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `<9.1.2,>=9.1.1` → `<9.2.1,>=9.2.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/PwnedPW/pulls/368 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `<9.1.2,>=9.1.1` → `<9.2.1,>=9.2.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/webexmemebot/pulls/631 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `<9.1.2,>=9.1.1` → `<9.2.1,>=9.2.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/pypilot/pulls/493 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `<9.1.2,>=9.1.1` → `<9.2.1,>=9.2.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/epage/pulls/256 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `<9.1.2,>=9.1.1` → `<9.2.1,>=9.2.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/luke/instant-msg-api/pulls/297 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `<9.1.2,>=9.1.1` → `<9.2.1,>=9.2.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/roboluke/pulls/494 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `>=9.1,<9.2` → `>=9.2,<9.3` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.2.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.1.1/9.2.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](pytest-dev/pytest@9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](pytest-dev/pytest#14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](pytest-dev/pytest#2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](pytest-dev/pytest#12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#14675), [#14953](pytest-dev/pytest#14953), [#15153](pytest-dev/pytest#15153), [#15132](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](pytest-dev/pytest#10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](pytest-dev/pytest#14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](pytest-dev/pytest#14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](pytest-dev/pytest#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](pytest-dev/pytest#14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#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-dev/pytest#15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](pytest-dev/pytest#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](pytest-dev/pytest#15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](pytest-dev/pytest#15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](pytest-dev/pytest#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](pytest-dev/pytest#15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](pytest-dev/pytest#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](pytest-dev/pytest#6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](pytest-dev/pytest#6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](pytest-dev/pytest#7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](pytest-dev/pytest#10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](pytest-dev/pytest#12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](pytest-dev/pytest#12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](pytest-dev/pytest#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](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](pytest-dev/pytest#15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](pytest-dev/pytest#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-dev/pytest#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](pytest-dev/pytest#9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](pytest-dev/pytest#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](pytest-dev/pytest#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](pytest-dev/pytest#14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](pytest-dev/pytest#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](pytest-dev/pytest#15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](pytest-dev/pytest#13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](pytest-dev/pytest#14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/labmcp/pulls/85 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>

RonnyPfannschmidt force-pushed the ronny/assert-rewrite-coverage-harness branch from dc66953 to 2c2d51e Compare July 31, 2026 19:01

pyba-chronographer Bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Jul 31, 2026

RonnyPfannschmidt force-pushed the ronny/assert-rewrite-coverage-harness branch from 2c2d51e to ff0f7c0 Compare July 31, 2026 20:12

This was referenced Jul 31, 2026

fix(rewrite): freeze operands against any later side effect #14821

Draft

fix(rewrite): short-circuit chained comparisons #14822

Draft

RonnyPfannschmidt marked this pull request as ready for review August 12, 2026 07:57

RonnyPfannschmidt requested a review from The-Compiler August 12, 2026 07:57

bluetech reviewed Aug 15, 2026

View reviewed changes

RonnyPfannschmidt force-pushed the ronny/assert-rewrite-coverage-harness branch from a3b7edc to 8c204fa Compare August 20, 2026 04:35

RonnyPfannschmidt mentioned this pull request Aug 20, 2026

test(rewrite): record the introspection gaps nothing fixes yet #14916

Draft

bluetech approved these changes Aug 20, 2026

View reviewed changes

RonnyPfannschmidt merged commit df87db7 into pytest-dev:main Aug 20, 2026
36 checks passed

RonnyPfannschmidt deleted the ronny/assert-rewrite-coverage-harness branch October 4, 2026 17:35

Navigation Menu

Repository navigation

test(rewrite): systematic coverage matrix for assertion rewriting - #14813

test(rewrite): systematic coverage matrix for assertion rewriting#14813
RonnyPfannschmidt merged 1 commit into
pytest-dev:mainfrom
RonnyPfannschmidt:ronny/assert-rewrite-coverage-harness

RonnyPfannschmidt commented Jul 31, 2026 •

edited

Loading

Uh oh!

bluetech left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

RonnyPfannschmidt commented Aug 20, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

RonnyPfannschmidt commented Jul 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

The evaluation-order axis is new

Only what passes

No behaviour change

Uh oh!

bluetech left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

RonnyPfannschmidt commented Aug 20, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

RonnyPfannschmidt commented Jul 31, 2026 •

edited

Loading