add paramspec to callable forms of raises/warns/deprecated_call, rewrite tests to use CM form by jakkdl · Pull Request #13241 · pytest-dev/pytest

jakkdl · 2025-02-20T10:11:22Z

deprecation

~~Deprecates the legacy callable forms for pytest.raises, pytest.warns and pytest.deprecated_call, and~~ replaces all instances in the code base of them aside from code specifically for testing them.

paramspec

pytest.raises, warns & deprecated_call previously typed *args and **kwargs as Any in the legacy callable form, so this did not raise errors:

def foo(x: int) -> None:
    raise ValueError
raises(ValueError, foo, None)

but now it will give call-overload.

It also makes it possible to pass func as a kwarg, which the type hints previously showed as possible, but it didn't work.

It's possible that func (and the expected type?) should be pos-only, as this looks quite weird:

raises(1, 2, kwarg1=3, func=my_func, kwarg2=4, expected_exception=ValueError)

but if somebody is dynamically generating parameters to send to raises then we probably shouldn't ban it needlessly; and we can't make func pos-only without making expected_exception pos-only, and that could break backwards compatibility.

Include documentation when adding new features.
Include new tests or update existing tests when applicable.
Allow maintainers to push and squash when merging my commits. Please uncheck this if you prefer to squash the commits yourself.
Create a new changelog file in the changelog folder, with a name like <ISSUE NUMBER>.<TYPE>.rst. See changelog/README.rst for details.

Noticed while working on #13192

RonnyPfannschmidt · 2025-02-20T10:53:47Z

I believe the key issue is that back when the api was initially created, neither typing nor POS only arguments where a thing

In hindsight, both func and expected exceptions should be POS only arguments

Some kind of deprecating overload would be needed (no cluesif typing supports anyof that)

I'm thinking whether we should just downright deprecate the call form

Back in python 2.5 times when we had no with statement there only was a call form and a exec form (multiline stringto eval)

Now that soon python 3.8 support is dropped we perhaps ought to just go context only and plan accordingly

jakkdl · 2025-02-20T15:24:33Z

I believe the key issue is that back when the api was initially created, neither typing nor POS only arguments where a thing

In hindsight, both func and expected exceptions should be POS only arguments

I could make them pos-only for RaisesExc and RaisesGroup in #13192 to start with, so we only need to do deprecation on pytest.raises itself.

Some kind of deprecating overload would be needed (no cluesif typing supports anyof that)

@warnings.deprecated does indeed allow for deprecating individual overloads.

I'm thinking whether we should just downright deprecate the call form

Back in python 2.5 times when we had no with statement there only was a call form and a exec form (multiline stringto eval)

Now that soon python 3.8 support is dropped we perhaps ought to just go context only and plan accordingly

the docs does say

This form was the original pytest.raises() API, developed before the with statement was added to the Python language. Nowadays, this form is rarely used, with the context-manager form (using with) being considered more readable. Nonetheless, this form is fully supported and not deprecated in any way.

(emphasis mine) which kind of sounds like us wanting to support it indefinitely, but I have never seen the form used outside of the pytest repo itself, so I think we should be plenty fine deprecating it.

jakkdl · 2025-02-21T17:10:40Z

"well, let's just deprecate them then!"
...

thankfully I had LLM generate a regex that did a lot of the replacements, but, uh, fun times.

I don't think there's much to gain from deprecating pytest.raises(expected_exception=ValueError)?

TODO:

Changelog
update PR title & description (lol)
update docs

jakkdl · 2025-02-24T11:50:53Z

the other stuff causing <100% diff coverage is me editing currently-uncovered code

nicoddemus

Thanks @jakkdl for tackling this.

Left comments mostly related to the docs.

However I wonder if we really should deprecate this functionality?

We never said it would deprecated.
Changing to the context manager is non-trivial to do, which will cause a lot of friction in older codebases.
The code to support the legacy form seems pretty minimal to me, so we gain little by removing the support.

So my vote on this is -0, as I think the disruption/friction outweighs the small benefit of removing the supporting code, but if everybody else thinks this is worthwhile, then I'm OK with it too.

nicoddemus · 2025-03-01T14:04:23Z

+if sys.version_info >= (3, 13):
+    from warnings import deprecated as deprecated
+elif TYPE_CHECKING:
+    from typing_extensions import deprecated as deprecated
+else:
+
+    def deprecated(reason: str = "") -> object:
+        def decorator(func: object) -> object:
+            return func
+
+        return decorator


warnings.deprecated will emit a warning at runtime in addition to be used by type checkers, but not for Python <= 3.12, which IIUC is a problem then.

Seems like the only solution is to always generate the runtime warning ourselves, and only rely on the deprecated decorator when TYPE_CHECKING?

hm, since this PR does manually raise the warning everywhere we should be getting double warnings on 3.13 ... and either the tests are not catching it or the second one is getting suppressed.

Ah, @deprecated is only being used together with @overload in this PR; so it is solely used for TYPE_CHECKING. I'll clarify that with comments/docstring in case somebody wants to use it more in the future

jakkdl · 2025-03-03T12:00:10Z

The code to support the legacy form seems pretty minimal to me, so we gain little by removing the support.

It's not a lot of supporting code at its face, but it took me a while to figure out gc troubles in 13192#2c8cd and raises could entirely be removed in place of a from ... export RaisesExc as raises after #13192.

It's also a question of whether to keep it maintained with RaisesExc - e.g. should it now accept the check parameter? If so, that will break code:

def my_fun(check):
    ...

def test_my_fun():
    pytest.raises(my_fun, check=5)

if we wanted to fully embrace it then maybe RaisesGroup should have a callable form, but that'd be kinda silly.

Changing to the context manager is non-trivial to do, which will cause a lot of friction in older codebases.

it'd be nice to get a sense of how prevalent it is, I've personally never encountered it outside of the pytest code base itself.

So my vote on this is -0, as I think the disruption/friction outweighs the small benefit of removing the supporting code, but if everybody else thinks this is worthwhile, then I'm OK with it too.

I agree that it's not a slam-dunk, and if we deprecate it we should make sure to have a long deprecation cycle. Heck, we could try deprecating it and if there's complaints we consider reversing. (futuredeprecationwarning? and/or a message explicitly saying so)

RonnyPfannschmidt · 2025-03-10T08:20:02Z

perhaps before deprecating we should see to have tools like ruff supply a code fix and/or have a ast-grep receipt to do the code fix

the code change itself is not that hard, but its a massive friction without a tool that does it

jakkdl · 2025-03-10T12:11:18Z

perhaps before deprecating we should see to have tools like ruff supply a code fix and/or have a ast-grep receipt to do the code fix

the code change itself is not that hard, but its a massive friction without a tool that does it

I like that, I'll go open some issues.
In order not to have this PR stall forever, let's do PendingDeprecationWarning for now.

edit: FutureDeprecationWarning -> PendingDeprecationWarning

RonnyPfannschmidt · 2025-03-10T17:08:05Z

Let's see if the future warning triggers any issues for users

I'm on board however python warning is quite some unexpected fun sometimes

jakkdl · 2025-03-11T15:34:31Z

hm, while the default python filter will hide PendingDeprecationWarning, it appears pytest does not. So having it be a PendingDeprecationWarning won't really change the direct impact to users, although we're signaling that they don't need to rush with a fix.

If we do want to hold off on even that then I should split this PR and we can merge the test changes + paramspec on their own

RonnyPfannschmidt · 2025-03-11T15:41:31Z

Let's put it in for now

We can put it on defer if there's a problematic impact most recent user's shouldn't be affected

jakkdl · 2025-03-11T16:54:12Z

codecov diff complaints are solely from me changing callable raises to cm-raises in code that's not covered on main/ - technically adding more uncovered lines

jakkdl · 2025-03-31T11:05:39Z

@nicoddemus ? :)

jakkdl · 2025-05-26T10:12:45Z

Ruff is actively working on a rule to autofix callable raises: astral-sh/ruff#17368

I also wrote a rule for flake8-pytest-style but have seen no response from maintainers: m-burst/flake8-pytest-style#332

So with ruff helping out I think there's no problem going ahead with this, we could possibly even suggest people make use of it in the error message

nicoddemus · 2025-05-27T00:21:06Z

 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+.. warning::
+   This will be deprecated and removed in a future release.


Suggested change

This will be deprecated and removed in a future release.

This form is deprecated and will be removed in a future release.

nicoddemus · 2025-05-27T00:26:27Z

@nicoddemus ? :)

Sorry, completely missed this.

To be perfectly honest, I'm still not 100% on board with this deprecation, but it seems I'm in the minority so I don't want to block this, especially because I'm not sure the impact will be that significant.

That said, it would be great to hear from other core team members (@pytest-dev/core) before we move forward.

bluetech · 2025-05-27T06:38:42Z

Thanks for the proposal @jakkdl. Sorry for not looking earlier, @nicoddemus's comment above prompted me to look.

Like @nicoddemus I also feel uneasy about deprecating the non-cm forms. The reason being, it will cause a lot of churn. There is a lot of code out there using these forms, and I think breaking old working code should only be done for very good reasons.

Looking at the PR I see 3 changes:

Improve typing of call form with ParamSpec.
Change pytest tests to not use call form
Deprecate

1 and 2 LGTM. For 1, IIUC it doesn't pose backward compat issues right? And for 2, we should keep tests that check that the call forms actually work, but not use it in other tests. So if you move these changes to a separate PR I think we can merge it.

As for 3, I am +1 on completely removing it from our docs. A lint would be great. I'm even +0.5 on completely hiding it from type checkers using if TYPE_CHECKING, this way it doesn't show up in autocomplete and docs, etc (this one maybe only after a lint is available). But I'm -1 on actual deprecation and eventual removal.

(This is not a hard block if other devs feel differently. And to be frank, I didn't really try to understand the RaisesGroup motivation you mentioned in #13241 (comment)...)

jakkdl · 2025-05-27T10:09:42Z

And just to double-check, you're also against doing PendingDeprecationWarning? (which is the current state of the PR, I just haven't updated the OP) @nicoddemus @bluetech

I kind of think it should be possible for us to deprecate it at some point, the callable form really is quite archaic at this point. But I'm not opposed to letting the lint loose and then perhaps revisiting this in a few years.

(This is not a hard block if other devs feel differently. And to be frank, I didn't really try to understand the RaisesGroup motivation you mentioned in #13241 (comment)...)

If we explicitly keep it on life-support I think that addresses most of my problems with keeping it around (i.e. don't need to care about updating it or anything).

RonnyPfannschmidt · 2025-05-27T10:22:05Z

Let's prepare to do the deprecation but shedule it for something like 9.y or a timeline

We should have a due date

bluetech · 2025-05-27T18:58:01Z

And just to double-check, you're also against doing PendingDeprecationWarning? (which is the current state of the PR, I just haven't updated the OP)

Since I don't see a reason to have a PendingDeprecationWarning if there is no intent to eventually fully deprecate, and I am against that, then I must be against PendingDeprecationWarning as well, if I claim to be logical :)

jakkdl · 2025-06-04T14:25:04Z

I thiiink I managed to cleanly separate out the deprecation, got it saved in a stash and will push it to a separate PR so it's saved somewhere if/when we want to do the deprecation.

I think the codecov misses looks good as well (i.e. any drop is due to uncovered code being longer), but would be nice to have an extra set of eyes on it.

bluetech

Thanks @jakkdl, LGTM. Only a comment about the doc change.

Just to make sure, did you keep some tests around specifically to verify that the legacy forms are still in working order?

jakkdl · 2025-06-10T13:16:10Z

Just to make sure, did you keep some tests around specifically to verify that the legacy forms are still in working order?

yep, there's a bunch of them in testing/python/raises.py. Though it might make sense to consolidate them in a single section, they're currently spread out in the file according to feature.

Found three more stray raises calls when git greping to confirm the above.

Use the nicer `with` forms instead.

We don't intend to deprecate the legacy forms, but there is no reason to use them anymore, and they add complexity/confusion, so let's just mostly pretend they don't exist in the docs.

…ted_call` `pytest.raises`, `warns` & `deprecated_call` previously typed `*args` and `**kwargs` as `Any` in the legacy callable form, so this did not raise errors: ```py def foo(x: int) -> None: raise ValueError raises(ValueError, foo, None) ``` but now it will give call-overload. It also makes it possible to pass `func` as a kwarg, which the type hints previously showed as possible, but it didn't work. It's possible that `func` (and the expected type?) should be pos-only, as this looks quite weird: ```py raises(1, 2, kwarg1=3, func=my_func, kwarg2=4, expected_exception=ValueError) ``` but if somebody is dynamically generating parameters to send to `raises` then we probably shouldn't ban it needlessly; and we can't make `func` pos-only without making `expected_exception` pos-only, and that could break backwards compatibility.

bluetech · 2026-04-09T15:42:03Z

I rebased to fix the conflicts, and split into 3 atomic commits. The previous CI results were gone, let's see what they say now.

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.0,>=9.0.0` → `<9.1.1,>=9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](pytest-dev/pytest@9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](pytest-dev/pytest#14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](pytest-dev/pytest#10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](pytest-dev/pytest#12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](pytest-dev/pytest#13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](pytest-dev/pytest#14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](pytest-dev/pytest#14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](pytest-dev/pytest#14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](pytest-dev/pytest#14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](pytest-dev/pytest#1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](pytest-dev/pytest#12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](pytest-dev/pytest#14023): Added --report-chars long CLI option. - [#14371](pytest-dev/pytest#14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](pytest-dev/pytest#6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](pytest-dev/pytest#8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](pytest-dev/pytest#11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](pytest-dev/pytest#11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](pytest-dev/pytest#13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](pytest-dev/pytest#13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](pytest-dev/pytest#14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](pytest-dev/pytest#14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](pytest-dev/pytest#14373): Added type annotations for `pytest.approx`. - [#14430](pytest-dev/pytest#14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](pytest-dev/pytest#14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](pytest-dev/pytest#14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](pytest-dev/pytest#14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](pytest-dev/pytest#14524): Add official Python 3.15 support. - [#1764](pytest-dev/pytest#1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](pytest-dev/pytest#8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](pytest-dev/pytest#13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](pytest-dev/pytest#13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](pytest-dev/pytest#13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](pytest-dev/pytest#13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](pytest-dev/pytest#13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](pytest-dev/pytest#13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](pytest-dev/pytest#13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](pytest-dev/pytest#13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](pytest-dev/pytest-xdist#1273). - [#14004](pytest-dev/pytest#14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](pytest-dev/pytest#14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](pytest-dev/pytest#14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](pytest-dev/pytest#14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](pytest-dev/pytest#14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](pytest-dev/pytest#14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](pytest-dev/pytest#14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](pytest-dev/pytest#14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](pytest-dev/pytest#14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](pytest-dev/pytest#14377): Fixed crash in Config.get\_terminal\_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](pytest-dev/pytest#14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](pytest-dev/pytest#14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](pytest-dev/pytest#14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](pytest-dev/pytest#14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](pytest-dev/pytest#14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](pytest-dev/pytest#14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](pytest-dev/pytest#14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](pytest-dev/pytest#14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](pytest-dev/pytest#3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](pytest-dev/pytest#3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](pytest-dev/pytest#5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](pytest-dev/pytest#719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](pytest-dev/pytest#11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](pytest-dev/pytest#11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](pytest-dev/pytest#13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](pytest-dev/pytest#13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](pytest-dev/pytest#13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](pytest-dev/pytest#13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](pytest-dev/pytest#14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](pytest-dev/pytest#14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](pytest-dev/pytest#14303): The documentation is now built with Sphinx >= 9. - [#14465](pytest-dev/pytest#14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](pytest-dev/pytest#14582): Improved the recursion traceback test to exercise all requested traceback styles. </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](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/PwnedPW/pulls/340 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk> Co-committed-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.0,>=9.0.0` → `<9.1.1,>=9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](pytest-dev/pytest@9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](pytest-dev/pytest#14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](pytest-dev/pytest#10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](pytest-dev/pytest#12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](pytest-dev/pytest#13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](pytest-dev/pytest#14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](pytest-dev/pytest#14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](pytest-dev/pytest#14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](pytest-dev/pytest#14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](pytest-dev/pytest#1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](pytest-dev/pytest#12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](pytest-dev/pytest#14023): Added --report-chars long CLI option. - [#14371](pytest-dev/pytest#14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](pytest-dev/pytest#6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](pytest-dev/pytest#8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](pytest-dev/pytest#11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](pytest-dev/pytest#11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](pytest-dev/pytest#13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](pytest-dev/pytest#13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](pytest-dev/pytest#14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](pytest-dev/pytest#14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](pytest-dev/pytest#14373): Added type annotations for `pytest.approx`. - [#14430](pytest-dev/pytest#14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](pytest-dev/pytest#14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](pytest-dev/pytest#14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](pytest-dev/pytest#14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](pytest-dev/pytest#14524): Add official Python 3.15 support. - [#1764](pytest-dev/pytest#1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](pytest-dev/pytest#8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](pytest-dev/pytest#13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](pytest-dev/pytest#13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](pytest-dev/pytest#13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](pytest-dev/pytest#13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](pytest-dev/pytest#13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](pytest-dev/pytest#13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](pytest-dev/pytest#13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](pytest-dev/pytest#13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](pytest-dev/pytest-xdist#1273). - [#14004](pytest-dev/pytest#14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](pytest-dev/pytest#14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](pytest-dev/pytest#14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](pytest-dev/pytest#14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](pytest-dev/pytest#14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](pytest-dev/pytest#14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](pytest-dev/pytest#14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](pytest-dev/pytest#14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](pytest-dev/pytest#14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](pytest-dev/pytest#14377): Fixed crash in Config.get\_terminal\_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](pytest-dev/pytest#14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](pytest-dev/pytest#14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](pytest-dev/pytest#14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](pytest-dev/pytest#14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](pytest-dev/pytest#14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](pytest-dev/pytest#14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](pytest-dev/pytest#14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](pytest-dev/pytest#14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](pytest-dev/pytest#3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](pytest-dev/pytest#3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](pytest-dev/pytest#5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](pytest-dev/pytest#719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](pytest-dev/pytest#11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](pytest-dev/pytest#11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](pytest-dev/pytest#13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](pytest-dev/pytest#13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](pytest-dev/pytest#13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](pytest-dev/pytest#13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](pytest-dev/pytest#14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](pytest-dev/pytest#14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](pytest-dev/pytest#14303): The documentation is now built with Sphinx >= 9. - [#14465](pytest-dev/pytest#14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](pytest-dev/pytest#14582): Improved the recursion traceback test to exercise all requested traceback styles. </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](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/pypilot/pulls/454 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk> Co-committed-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.0,>=9.0.0` → `<9.1.1,>=9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](pytest-dev/pytest@9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](pytest-dev/pytest#14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](pytest-dev/pytest#10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](pytest-dev/pytest#12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](pytest-dev/pytest#13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](pytest-dev/pytest#14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](pytest-dev/pytest#14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](pytest-dev/pytest#14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](pytest-dev/pytest#14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](pytest-dev/pytest#1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](pytest-dev/pytest#12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](pytest-dev/pytest#14023): Added --report-chars long CLI option. - [#14371](pytest-dev/pytest#14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](pytest-dev/pytest#6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](pytest-dev/pytest#8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](pytest-dev/pytest#11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](pytest-dev/pytest#11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](pytest-dev/pytest#13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](pytest-dev/pytest#13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](pytest-dev/pytest#14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](pytest-dev/pytest#14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](pytest-dev/pytest#14373): Added type annotations for `pytest.approx`. - [#14430](pytest-dev/pytest#14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](pytest-dev/pytest#14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](pytest-dev/pytest#14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](pytest-dev/pytest#14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](pytest-dev/pytest#14524): Add official Python 3.15 support. - [#1764](pytest-dev/pytest#1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](pytest-dev/pytest#8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](pytest-dev/pytest#13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](pytest-dev/pytest#13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](pytest-dev/pytest#13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](pytest-dev/pytest#13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](pytest-dev/pytest#13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](pytest-dev/pytest#13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](pytest-dev/pytest#13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](pytest-dev/pytest#13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](pytest-dev/pytest-xdist#1273). - [#14004](pytest-dev/pytest#14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](pytest-dev/pytest#14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](pytest-dev/pytest#14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](pytest-dev/pytest#14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](pytest-dev/pytest#14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](pytest-dev/pytest#14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](pytest-dev/pytest#14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](pytest-dev/pytest#14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](pytest-dev/pytest#14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](pytest-dev/pytest#14377): Fixed crash in Config.get\_terminal\_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](pytest-dev/pytest#14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](pytest-dev/pytest#14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](pytest-dev/pytest#14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](pytest-dev/pytest#14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](pytest-dev/pytest#14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](pytest-dev/pytest#14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](pytest-dev/pytest#14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](pytest-dev/pytest#14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](pytest-dev/pytest#3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](pytest-dev/pytest#3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](pytest-dev/pytest#5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](pytest-dev/pytest#719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](pytest-dev/pytest#11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](pytest-dev/pytest#11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](pytest-dev/pytest#13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](pytest-dev/pytest#13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](pytest-dev/pytest#13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](pytest-dev/pytest#13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](pytest-dev/pytest#14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](pytest-dev/pytest#14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](pytest-dev/pytest#14303): The documentation is now built with Sphinx >= 9. - [#14465](pytest-dev/pytest#14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](pytest-dev/pytest#14582): Improved the recursion traceback test to exercise all requested traceback styles. </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](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/epage/pulls/225 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk> Co-committed-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.0,>=9.0.0` → `<9.1.1,>=9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](pytest-dev/pytest@9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](pytest-dev/pytest#14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](pytest-dev/pytest#10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](pytest-dev/pytest#12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](pytest-dev/pytest#13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](pytest-dev/pytest#14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](pytest-dev/pytest#14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](pytest-dev/pytest#14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](pytest-dev/pytest#14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](pytest-dev/pytest#1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](pytest-dev/pytest#12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](pytest-dev/pytest#14023): Added --report-chars long CLI option. - [#14371](pytest-dev/pytest#14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](pytest-dev/pytest#6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](pytest-dev/pytest#8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](pytest-dev/pytest#11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](pytest-dev/pytest#11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](pytest-dev/pytest#13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](pytest-dev/pytest#13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](pytest-dev/pytest#14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](pytest-dev/pytest#14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](pytest-dev/pytest#14373): Added type annotations for `pytest.approx`. - [#14430](pytest-dev/pytest#14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](pytest-dev/pytest#14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](pytest-dev/pytest#14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](pytest-dev/pytest#14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](pytest-dev/pytest#14524): Add official Python 3.15 support. - [#1764](pytest-dev/pytest#1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](pytest-dev/pytest#8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](pytest-dev/pytest#13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](pytest-dev/pytest#13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](pytest-dev/pytest#13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](pytest-dev/pytest#13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](pytest-dev/pytest#13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](pytest-dev/pytest#13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](pytest-dev/pytest#13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](pytest-dev/pytest#13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](pytest-dev/pytest-xdist#1273). - [#14004](pytest-dev/pytest#14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](pytest-dev/pytest#14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](pytest-dev/pytest#14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](pytest-dev/pytest#14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](pytest-dev/pytest#14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](pytest-dev/pytest#14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](pytest-dev/pytest#14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](pytest-dev/pytest#14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](pytest-dev/pytest#14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](pytest-dev/pytest#14377): Fixed crash in Config.get\_terminal\_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](pytest-dev/pytest#14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](pytest-dev/pytest#14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](pytest-dev/pytest#14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](pytest-dev/pytest#14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](pytest-dev/pytest#14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](pytest-dev/pytest#14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](pytest-dev/pytest#14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](pytest-dev/pytest#14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](pytest-dev/pytest#3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](pytest-dev/pytest#3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](pytest-dev/pytest#5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](pytest-dev/pytest#719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](pytest-dev/pytest#11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](pytest-dev/pytest#11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](pytest-dev/pytest#13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](pytest-dev/pytest#13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](pytest-dev/pytest#13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](pytest-dev/pytest#13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](pytest-dev/pytest#14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](pytest-dev/pytest#14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](pytest-dev/pytest#14303): The documentation is now built with Sphinx >= 9. - [#14465](pytest-dev/pytest#14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](pytest-dev/pytest#14582): Improved the recursion traceback test to exercise all requested traceback styles. </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](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/luke/instant-msg-api/pulls/263 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk> Co-committed-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.0,>=9.0.0` → `<9.1.1,>=9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](pytest-dev/pytest@9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](pytest-dev/pytest#14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](pytest-dev/pytest#10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](pytest-dev/pytest#12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](pytest-dev/pytest#13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](pytest-dev/pytest#14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](pytest-dev/pytest#14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](pytest-dev/pytest#14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](pytest-dev/pytest#14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](pytest-dev/pytest#1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](pytest-dev/pytest#12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](pytest-dev/pytest#14023): Added --report-chars long CLI option. - [#14371](pytest-dev/pytest#14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](pytest-dev/pytest#6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](pytest-dev/pytest#8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](pytest-dev/pytest#11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](pytest-dev/pytest#11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](pytest-dev/pytest#13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](pytest-dev/pytest#13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](pytest-dev/pytest#14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](pytest-dev/pytest#14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](pytest-dev/pytest#14373): Added type annotations for `pytest.approx`. - [#14430](pytest-dev/pytest#14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](pytest-dev/pytest#14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](pytest-dev/pytest#14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](pytest-dev/pytest#14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](pytest-dev/pytest#14524): Add official Python 3.15 support. - [#1764](pytest-dev/pytest#1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](pytest-dev/pytest#8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](pytest-dev/pytest#13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](pytest-dev/pytest#13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](pytest-dev/pytest#13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](pytest-dev/pytest#13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](pytest-dev/pytest#13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](pytest-dev/pytest#13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](pytest-dev/pytest#13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](pytest-dev/pytest#13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](pytest-dev/pytest-xdist#1273). - [#14004](pytest-dev/pytest#14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](pytest-dev/pytest#14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](pytest-dev/pytest#14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](pytest-dev/pytest#14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](pytest-dev/pytest#14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](pytest-dev/pytest#14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](pytest-dev/pytest#14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](pytest-dev/pytest#14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](pytest-dev/pytest#14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](pytest-dev/pytest#14377): Fixed crash in Config.get\_terminal\_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](pytest-dev/pytest#14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](pytest-dev/pytest#14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](pytest-dev/pytest#14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](pytest-dev/pytest#14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](pytest-dev/pytest#14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](pytest-dev/pytest#14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](pytest-dev/pytest#14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](pytest-dev/pytest#14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](pytest-dev/pytest#3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](pytest-dev/pytest#3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](pytest-dev/pytest#5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](pytest-dev/pytest#719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](pytest-dev/pytest#11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](pytest-dev/pytest#11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](pytest-dev/pytest#13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](pytest-dev/pytest#13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](pytest-dev/pytest#13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](pytest-dev/pytest#13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](pytest-dev/pytest#14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](pytest-dev/pytest#14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](pytest-dev/pytest#14303): The documentation is now built with Sphinx >= 9. - [#14465](pytest-dev/pytest#14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](pytest-dev/pytest#14582): Improved the recursion traceback test to exercise all requested traceback styles. </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](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/webexmemebot/pulls/590 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk> Co-committed-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.0,>=9.0.0` → `<9.1.1,>=9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](pytest-dev/pytest@9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](pytest-dev/pytest#14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](pytest-dev/pytest#10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](pytest-dev/pytest#12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](pytest-dev/pytest#13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](pytest-dev/pytest#13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](pytest-dev/pytest#14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](pytest-dev/pytest#14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](pytest-dev/pytest#14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](pytest-dev/pytest#14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](pytest-dev/pytest#1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](pytest-dev/pytest#12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](pytest-dev/pytest#14023): Added --report-chars long CLI option. - [#14371](pytest-dev/pytest#14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](pytest-dev/pytest#6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](pytest-dev/pytest#8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](pytest-dev/pytest#11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](pytest-dev/pytest#11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](pytest-dev/pytest#13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](pytest-dev/pytest#13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](pytest-dev/pytest#14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](pytest-dev/pytest#14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](pytest-dev/pytest#14373): Added type annotations for `pytest.approx`. - [#14430](pytest-dev/pytest#14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](pytest-dev/pytest#14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](pytest-dev/pytest#14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](pytest-dev/pytest#14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](pytest-dev/pytest#14524): Add official Python 3.15 support. - [#1764](pytest-dev/pytest#1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](pytest-dev/pytest#8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](pytest-dev/pytest#13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](pytest-dev/pytest#13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](pytest-dev/pytest#13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](pytest-dev/pytest#13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](pytest-dev/pytest#13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](pytest-dev/pytest#13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](pytest-dev/pytest#13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](pytest-dev/pytest#13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](pytest-dev/pytest-xdist#1273). - [#14004](pytest-dev/pytest#14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](pytest-dev/pytest#14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](pytest-dev/pytest#14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](pytest-dev/pytest#14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](pytest-dev/pytest#14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](pytest-dev/pytest#14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](pytest-dev/pytest#14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](pytest-dev/pytest#14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](pytest-dev/pytest#14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](pytest-dev/pytest#14377): Fixed crash in Config.get\_terminal\_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](pytest-dev/pytest#14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](pytest-dev/pytest#14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](pytest-dev/pytest#14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](pytest-dev/pytest#14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](pytest-dev/pytest#14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](pytest-dev/pytest#14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](pytest-dev/pytest#14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](pytest-dev/pytest#14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](pytest-dev/pytest#3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](pytest-dev/pytest#3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](pytest-dev/pytest#5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](pytest-dev/pytest#719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](pytest-dev/pytest#11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](pytest-dev/pytest#11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](pytest-dev/pytest#13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](pytest-dev/pytest#13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](pytest-dev/pytest#13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](pytest-dev/pytest#13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](pytest-dev/pytest#14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](pytest-dev/pytest#14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](pytest-dev/pytest#14303): The documentation is now built with Sphinx >= 9. - [#14465](pytest-dev/pytest#14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](pytest-dev/pytest#14582): Improved the recursion traceback test to exercise all requested traceback styles. </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](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.tainton.uk/repos/roboluke/pulls/456 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk> Co-committed-by: renovate[bot] <renovate-bot@git.tainton.uk>

jakkdl added the topic: typing type-annotation issue label Feb 20, 2025

jakkdl requested review from Zac-HD and nicoddemus February 20, 2025 10:11

psf-chronographer Bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Feb 20, 2025

jakkdl changed the title ~~add paramspec to non-cm raises~~ deprecate non-cm raises,warns&deprecated call + add paramspec Feb 24, 2025

jakkdl requested a review from RonnyPfannschmidt February 24, 2025 11:51

webknjaz reviewed Feb 24, 2025

View reviewed changes

Comment thread doc/en/deprecations.rst Outdated

webknjaz reviewed Feb 24, 2025

View reviewed changes

Comment thread src/_pytest/recwarn.py Outdated

nicoddemus requested changes Mar 1, 2025

View reviewed changes

This was referenced Mar 10, 2025

I want a rule that will warn on non-cm use of pytest.raises m-burst/flake8-pytest-style#331

Open

Autofix non-contextmanager use of pytest.raises & friends astral-sh/ruff#16605

Closed

jakkdl requested a review from nicoddemus March 11, 2025 16:54

webknjaz mentioned this pull request Apr 18, 2025

[ruff] Check for non-context-manager use of pytest.raises, pytest.warns, and pytest.deprecated_call (RUF061) astral-sh/ruff#17368

Merged

nicoddemus reviewed May 27, 2025

View reviewed changes

bluetech reviewed May 27, 2025

View reviewed changes

Comment thread src/_pytest/python_api.py Outdated

jakkdl force-pushed the raises_paramspec branch from ded3c05 to ee00946 Compare June 4, 2025 13:26

jakkdl changed the title ~~deprecate non-cm raises,warns&deprecated call + add paramspec~~ add paramspec to callable forms of raises/warns/deprecated_call, rewrite tests to use CM form Jun 4, 2025

jakkdl added skip news used on prs to opt out of the changelog requirement and removed skip news used on prs to opt out of the changelog requirement labels Jun 4, 2025

jakkdl requested a review from nicoddemus June 4, 2025 14:25

bluetech reviewed Jun 6, 2025

View reviewed changes

Comment thread doc/en/how-to/assert.rst Outdated

Comment thread src/_pytest/recwarn.py Outdated

bluetech approved these changes Jun 10, 2025

View reviewed changes

RonnyPfannschmidt approved these changes Jun 12, 2025

View reviewed changes

jakkdl added 3 commits April 9, 2026 18:34

testing: avoid legacy forms of warns, raises, deprecated_call

2b5952c

Use the nicer `with` forms instead.

doc: undocument legacy forms of raises, warns, deprecated_call

d42cef1

We don't intend to deprecate the legacy forms, but there is no reason to use them anymore, and they add complexity/confusion, so let's just mostly pretend they don't exist in the docs.

bluetech force-pushed the raises_paramspec branch from 363b89b to f7f0889 Compare April 9, 2026 15:41

bluetech merged commit 4cbef64 into pytest-dev:main Apr 9, 2026
32 of 33 checks passed

jakkdl deleted the raises_paramspec branch April 13, 2026 13:53

	This will be deprecated and removed in a future release.
	This form is deprecated and will be removed in a future release.

Uh oh!

Uh oh!

Conversation

jakkdl commented Feb 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

deprecation

paramspec

Uh oh!

RonnyPfannschmidt commented Feb 20, 2025

Uh oh!

jakkdl commented Feb 20, 2025

Uh oh!

jakkdl commented Feb 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jakkdl commented Feb 24, 2025

Uh oh!

Uh oh!

Uh oh!

nicoddemus left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

nicoddemus Mar 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jakkdl Mar 3, 2025

Choose a reason for hiding this comment

Uh oh!

jakkdl Mar 11, 2025

Choose a reason for hiding this comment

Uh oh!

jakkdl commented Mar 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

RonnyPfannschmidt commented Mar 10, 2025

Uh oh!

jakkdl commented Mar 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

RonnyPfannschmidt commented Mar 10, 2025

Uh oh!

jakkdl commented Mar 11, 2025

Uh oh!

RonnyPfannschmidt commented Mar 11, 2025

Uh oh!

jakkdl commented Mar 11, 2025

Uh oh!

jakkdl commented Mar 31, 2025

Uh oh!

jakkdl commented May 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nicoddemus May 27, 2025

Choose a reason for hiding this comment

Uh oh!

nicoddemus commented May 27, 2025

Uh oh!

bluetech commented May 27, 2025

Uh oh!

Uh oh!

jakkdl commented May 27, 2025

Uh oh!

RonnyPfannschmidt commented May 27, 2025

Uh oh!

bluetech commented May 27, 2025

Uh oh!

jakkdl commented Jun 4, 2025

Uh oh!

bluetech left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

jakkdl commented Feb 20, 2025 •

edited

Loading

jakkdl commented Feb 21, 2025 •

edited

Loading

nicoddemus Mar 1, 2025 •

edited

Loading

jakkdl commented Mar 3, 2025 •

edited

Loading

jakkdl commented Mar 10, 2025 •

edited

Loading

jakkdl commented May 26, 2025 •

edited

Loading