reduce gc_collect_harder default to 1 on CPython#14441
Merged
bluetech merged 3 commits intoMay 24, 2026
Merged
Conversation
Contributor
Author
|
Draft, since I'm not certain this is a good idea. |
Member
|
Im nit familiar with the plugin myself |
Contributor
Author
|
Unknown - I'm looking at history, and there's already once case that resets it to 0 no matter what - #13482 |
Member
|
I was uneasy with the multiple gc rounds but I couldn't entirely demonstrate the slowdown. But for me your report is sufficient. The unraisableexception plugin is non-deterministic and doing multiple gc rounds trying to make it so just seems too heavy. So basically +1 from me. I would also not add a special case for PyPI. |
Member
|
See also 391324e. Also cc @graingert. |
Member
|
Thanks for the CC, I have no opinion on this though |
The 5-iteration default was borrowed from the Trio project, where it was determined empirically to handle PyPy's object resurrection behavior: on PyPy, objects like coroutines can survive GC rounds because executing their __del__ can resurrect them. On CPython, reference counting frees most objects immediately. One GC pass is sufficient to handle reference cycles, as confirmed by all test_unraisableexception tests passing (including the refcycle variants). Use 1 pass on CPython and retain 5 on PyPy. Signed-off-by: Mike Fiedler <miketheman@gmail.com>
miketheman
force-pushed
the
miketheman/speed-up-test-sutie
branch
from
07255a2 to
e2bc38b
Compare
Using `timeit`, I found a faster call:
```python
import sys
import timeit
def method_hasattr():
return 5 if hasattr(sys, "pypy_version_info") else 1
def method_implementation():
return 5 if sys.implementation.name == "pypy" else 1
time1 = timeit.timeit(method_hasattr, number=10000)
time2 = timeit.timeit(method_implementation, number=10000)
print(f"Method Hasattr: {time1:.5f} seconds")
print(f"Method Implementation: {time2:.5f} seconds")
```
Results:
```
$ PYENV_VERSION=3.14.5 python microbench.py
Method Hasattr: 0.00085 seconds
Method Implementation: 0.00054 seconds
$ PYENV_VERSION=pypy3.11-7.3.22 python microbench.py
Method Hasattr: 0.00768 seconds
Method Implementation: 0.00070 seconds
```
Refs: https://docs.python.org/3/library/sys.html#sys.implementation
Signed-off-by: Mike Fiedler <miketheman@gmail.com>
Signed-off-by: Mike Fiedler <miketheman@gmail.com>
psf-chronographer
Bot
added
the
bot:chronographer:provided
Contributor
Author
|
I found a faster implementation, and added a changelog entry. If there's a benchamrking/test suite somewhere I can hook into, I'd be happy to explore that, but I didn't find one, so pointers would be appreciated. |
Contributor
Author
|
CI results compared:
Table 1: Total Job Time (wall clock)Table 2: Test Step Only (excludes setup/checkout/install/upload)Table 3: Test Step Summary by PlatformKey takeaways:
The signal is clear and consistent on Linux where runners are stable. Comparison script (uses Details#!/usr/bin/env python3
"""Compare test step timings between two GitHub Actions workflow runs.
Usage:
python scripts/compare_ci_runs.py <upstream_run_id> <our_run_id> [--repo REPO]
Example:
python scripts/compare_ci_runs.py 26336401841 26344890356
python scripts/compare_ci_runs.py 26336401841 26344890356 --repo pytest-dev/pytest
Requires: gh CLI authenticated with repo read access.
"""
from __future__ import annotations
import argparse
import json
import subprocess
import sys
from datetime import datetime
def secs(a: str | None, b: str | None) -> int | None:
if not a or not b:
return None
fmt = "%Y-%m-%dT%H:%M:%SZ"
try:
return int((datetime.strptime(b, fmt) - datetime.strptime(a, fmt)).total_seconds())
except ValueError:
return None
def fmt_secs(s: int | None) -> str:
if s is None:
return "—"
m, sec = divmod(s, 60)
return f"{m}m{sec:02d}s"
def delta_fmt(before: int | None, after: int | None) -> str:
if before is None or after is None:
return "—"
d = after - before
prefix = "+" if d >= 0 else "-"
m, s = divmod(abs(d), 60)
return f"{prefix}{m}m{s:02d}s" if m else f"{prefix}{s}s"
def pct(before: int | None, after: int | None) -> str:
if not before or after is None:
return "—"
p = ((after - before) / before) * 100
return f"{'+' if p > 0 else ''}{p:.1f}%"
def get_jobs(run_id: int, repo: str) -> list[dict]:
result = subprocess.run(
["gh", "run", "view", str(run_id), "--repo", repo, "--json", "jobs"],
capture_output=True,
text=True,
check=True,
)
return json.loads(result.stdout)["jobs"]
def parse_jobs(jobs: list[dict]) -> dict[str, dict]:
parsed = {}
for job in jobs:
if not job["name"].startswith("build"):
continue
job_secs = secs(job["startedAt"], job["completedAt"])
test_secs_total = sum(
secs(s["startedAt"], s["completedAt"]) or 0
for s in job["steps"]
if s["name"].startswith("Test ")
and (secs(s["startedAt"], s["completedAt"]) or 0) > 0
)
parsed[job["name"]] = {
"job_secs": job_secs,
"test_secs": test_secs_total or None,
}
return parsed
PLATFORM_GROUPS = {
"Linux (full suite)": ["ubuntu-py310", "ubuntu-py311", "ubuntu-py312", "ubuntu-py313", "ubuntu-py314"],
"Linux (variants)": [
"ubuntu-py310-freeze", "ubuntu-py310-lsof-numpy-pexpect", "ubuntu-py310-pluggy",
"ubuntu-py310-unittest-asynctest", "ubuntu-py310-unittest-twisted24",
"ubuntu-py310-unittest-twisted25", "ubuntu-py310-xdist", "ubuntu-py313-pexpect",
"ubuntu-pypy3-xdist",
],
"macOS": ["macos-py310", "macos-py312", "macos-py313", "macos-py314"],
"Windows": [
"windows-py310-pluggy", "windows-py310-unittest-asynctest", "windows-py310-unittest-twisted24",
"windows-py310-unittest-twisted25", "windows-py310-xdist", "windows-py311",
"windows-py312", "windows-py313", "windows-py314",
],
}
def get_group(short_name: str) -> str:
for group, members in PLATFORM_GROUPS.items():
if short_name in members:
return group
return "Other"
def print_table(headers: list[str], rows: list[list[str]], footer: list[str] | None = None) -> None:
widths = [max(len(str(row[i])) for row in ([headers] + rows + ([footer] if footer else []))) for i in range(len(headers))]
sep = "-" * (sum(widths) + 3 * len(widths) + 1)
fmt = " " + " ".join(f"{{:<{widths[0]}}}" if i == 0 else f"{{:>{widths[i]}}}" for i in range(len(headers)))
print(fmt.format(*headers))
print(sep)
for row in rows:
print(fmt.format(*row))
if footer:
print(sep)
print(fmt.format(*footer))
def main() -> None:
parser = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
parser.add_argument("upstream_run_id", type=int)
parser.add_argument("our_run_id", type=int)
parser.add_argument("--repo", default="pytest-dev/pytest")
args = parser.parse_args()
repo = args.repo
upstream_url = f"https://github.com/{repo}/actions/runs/{args.upstream_run_id}"
our_url = f"https://github.com/{repo}/actions/runs/{args.our_run_id}"
print(f"Fetching upstream run {args.upstream_run_id}...")
upstream = parse_jobs(get_jobs(args.upstream_run_id, repo))
print(f"Fetching our run {args.our_run_id}...")
ours = parse_jobs(get_jobs(args.our_run_id, repo))
all_names = sorted(set(upstream) | set(ours))
print(f"\n{'=' * 90}")
print(f"UPSTREAM: {upstream_url}")
print(f"OURS: {our_url}")
print(f"{'=' * 90}")
# Table 1: total job time
print("\n### Table 1: Total Job Time (wall clock)\n")
rows, total_u, total_o = [], 0, 0
for name in all_names:
short = name.removeprefix("build (").removesuffix(")")
u, o = upstream.get(name, {}), ours.get(name, {})
uj, oj = u.get("job_secs"), o.get("job_secs")
if uj: total_u += uj
if oj: total_o += oj
note = " [PyPy]" if "pypy" in name else ""
rows.append([short + note, fmt_secs(uj), fmt_secs(oj), delta_fmt(uj, oj), pct(uj, oj)])
print_table(
["Job", "Upstream", "Ours", "Delta", "% Change"],
rows,
["TOTAL (sum of all jobs)", fmt_secs(total_u), fmt_secs(total_o), delta_fmt(total_u, total_o), pct(total_u, total_o)],
)
# Table 2: test step only
print("\n\n### Table 2: Test Step Duration Only (excludes setup/checkout/install/upload)\n")
rows, total_u, total_o = [], 0, 0
for name in all_names:
short = name.removeprefix("build (").removesuffix(")")
u, o = upstream.get(name, {}), ours.get(name, {})
ut, ot = u.get("test_secs"), o.get("test_secs")
if ut: total_u += ut
if ot: total_o += ot
note = " [PyPy]" if "pypy" in name else ""
rows.append([short + note, fmt_secs(ut), fmt_secs(ot), delta_fmt(ut, ot), pct(ut, ot)])
print_table(
["Job", "Upstream", "Ours", "Delta", "% Change"],
rows,
["TOTAL (sum of all test steps)", fmt_secs(total_u), fmt_secs(total_o), delta_fmt(total_u, total_o), pct(total_u, total_o)],
)
# Table 3: by platform
print("\n\n### Table 3: Test Step Summary by Platform\n")
group_u: dict[str, int] = {}
group_o: dict[str, int] = {}
for name in all_names:
short = name.removeprefix("build (").removesuffix(")")
g = get_group(short)
group_u[g] = group_u.get(g, 0) + (upstream.get(name, {}).get("test_secs") or 0)
group_o[g] = group_o.get(g, 0) + (ours.get(name, {}).get("test_secs") or 0)
rows, gtot_u, gtot_o = [], 0, 0
for g in [*PLATFORM_GROUPS, "Other"]:
gu, go = group_u.get(g, 0), group_o.get(g, 0)
gtot_u += gu
gtot_o += go
rows.append([g, fmt_secs(gu), fmt_secs(go), delta_fmt(gu, go), pct(gu, go)])
print_table(
["Group", "Upstream (test)", "Ours (test)", "Saved", "%"],
rows,
["TOTAL", fmt_secs(gtot_u), fmt_secs(gtot_o), delta_fmt(gtot_u, gtot_o), pct(gtot_u, gtot_o)],
)
if __name__ == "__main__":
main() |
paulzuradzki
added a commit
to paulzuradzki/pytest
that referenced
this pull request
May 24, 2026
…gure pytest-dev#14441 reduced the default gc_collect_harder passes to 1 on CPython (5 on PyPy, where __del__ can resurrect objects). That change lived in cleanup(), which this branch emptied when it moved GC into pytest_unconfigure. Carry the same default into the new location so the relocation does not silently revert pytest-dev#14441. CPython still collects the refcycle regression tests in a single pass.
Zac-HD
pushed a commit
that referenced
this pull request
May 27, 2026
* Add failing regression test for #14263 (red) filterwarnings = error::ResourceWarning does not fail tests that leak resources through a reference cycle. collect_unraisable wraps the captured ResourceWarning in PytestUnraisableExceptionWarning, a class the user has no filter for, so the run exits 0. This test pins that contract: on a refcycle-leaking test with error::ResourceWarning configured, pytest should exit non-zero and the output should show the inner ResourceWarning rather than the wrapping PytestUnraisableExceptionWarning. Fails at this commit; the next commit ships the fix that turns it green. Refs #14263. * Surface filter-promoted unraisable warnings directly (#14263) When sys.unraisablehook captures a Warning subclass instance and the user has an active ``error::<that class>`` filter, raise the original warning rather than wrapping in PytestUnraisableExceptionWarning. The wrap path remains for any case where no matching error filter is set, so suites that don't use ``error::<warning>`` filters see no change. Filter matching is approximate: category only, not message/module/lineno. The check errs toward false negatives, never false positives. The regression test added in the previous commit now passes. Additional coverage: - test_refcycle_userwarning_filter: locks the contract for a non-builtin Warning subclass. - test_unraisable_warning_without_filter_still_wraps: scope guard. A Warning raised from __del__ without a matching error filter must still be wrapped, not raised directly. - test_unraisable_warning_filter_add_note_dedups: covers the duplicate- note guard in the unwrap path for singleton/cached Warning instances. Tightens the ``errors`` list type from list[Exception] to list[Warning | RuntimeError]. Adds Paul Zuradzki to AUTHORS. Notes in test_create_task_raises_unraisable_warning_filter that the propagated class is now bare RuntimeWarning rather than the wrapping PytestUnraisableExceptionWarning (because -Werror activates the new unwrap path). Closes #14263. * Add failing regression test for cleanup-stack ordering (red) Forces the bad LIFO order with a conftest that registers a warnings.resetwarnings cleanup via @hookimpl(trylast=True): it pops before unraisableexception's cleanup and clears the user's error::ResourceWarning filter before GC runs, so the leak exits 0. The next commit moves GC into pytest_unconfigure (runs before the cleanup stack closes), making the test pass regardless of plugin order. Refs #14263. * Move unraisable GC to pytest_unconfigure (refs #14263) Register only the hook-restore + stash-cleanup as the config.add_cleanup callback. Move the GC pump and collect_unraisable call into a new pytest_unconfigure(config) hook. pytest_unconfigure fires before _cleanup_stack.close(), so warning filters managed via the cleanup stack (the warnings plugin's catch_warnings context, in particular) are guaranteed active when GC runs. This decouples the unraisable step from plugin registration order in default_plugins. The previous arrangement worked only because of LIFO ordering on _cleanup_stack; #13057 (Dec 2024) reordered default_plugins to make that ordering correct, but the structural fragility remained. No observable behavior change. The 141 existing tests in test_unraisableexception + test_warnings + test_recwarn + test_threadexception still pass. The previous commit's test_refcycle_resource_warning_filter continues to fail on main and pass here. This is the structural side of the issue's two proposed fixes; the user-visible side shipped in the previous commit. * Add failing regression test for unset stash guard (red) After GC moved into pytest_unconfigure, a plugin whose pytest_configure raises UsageError leaves the stash key unset while pytest_unconfigure still runs. Without a presence check it hits KeyError and reports INTERNALERROR instead of USAGE_ERROR. The next commit adds the guard. Refs #14263. * Guard pytest_unconfigure against unset stash (refs #14263) When another plugin's pytest_configure raises (e.g. pytest.UsageError in testing/acceptance_test.py::test_config_error), pluggy skips remaining configure hooks. unraisableexception.pytest_configure never runs, config.stash[unraisable_exceptions] is never set. The previous config.add_cleanup callback wasn't registered in that case either, so cleanup was a no-op. The pytest_unconfigure hook introduced in the previous commit ran unconditionally and hit KeyError on the unset stash, surfacing as INTERNAL_ERROR where pytest should exit with USAGE_ERROR. Guard with a stash-presence check at the top of pytest_unconfigure. test_config_error catches the regression direction. * Tighten comments in unraisableexception * Add failure messages to result.ret assertions * Adopt #14441's CPython gc_collect default in pytest_unconfigure #14441 reduced the default gc_collect_harder passes to 1 on CPython (5 on PyPy, where __del__ can resurrect objects). That change lived in cleanup(), which this branch emptied when it moved GC into pytest_unconfigure. Carry the same default into the new location so the relocation does not silently revert #14441. CPython still collects the refcycle regression tests in a single pass. * PR feedback: keep GC in cleanup(), drop direct-raise of unraisable warnings Reviewer feedback on #14499: - Keep the GC + queue drain in cleanup() as well as pytest_unconfigure, so objects freed while the cleanup stack unwinds still surface. - Drop the direct-raise path (_warning_class_has_error_filter plus the unwrap branch in collect_unraisable). Re-raising the inner warning lost the traceback the hook captures as a string, and the filter match was only approximate. collect_unraisable now always wraps in PytestUnraisableExceptionWarning and lets the warnings machinery decide. Tests dropped or reworked: - Removed test_refcycle_resource_warning_filter: with only error::ResourceWarning the leak no longer fails the suite, which was the dropped direct-raise. - Removed test_refcycle_userwarning_filter: redundant with test_refcycle_unraisable_warning_filter once the wrapper is always raised. - Removed test_unraisable_warning_filter_add_note_dedups: covered the deleted add_note code. - Reworked test_unraisable_decouples_from_cleanup_stack_order to raise ValueError from __del__ and filter on error::pytest.PytestUnraisableExceptionWarning. A ResourceWarning leak only enters the unraisable pipeline through an error::ResourceWarning filter, which no longer promotes the wrapper; a raised exception is wrapped unconditionally, so the timing fix stays observable. Changelog reworded to describe the pytest_unconfigure timing fix instead of the dropped direct-raise behavior.
luketainton
pushed a commit
to luketainton/repos_PwnedPW
that referenced
this pull request
Jun 18, 2026
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` |  |  | --- ### 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 <span class="title-ref">--doctest-modules</span>, 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 <span class="title-ref">--report-chars</span> 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 <span class="title-ref">repr</span>. - [#​14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#​14137](pytest-dev/pytest#14137): <span class="title-ref">pytest.ScopeName</span> 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 <span class="title-ref">|</span> (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 <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize. - [#​13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> 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 <span class="title-ref">Config.get\_terminal\_writer</span> 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMjAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIyMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ1bml0LXRlc3RzIl19--> 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>
luketainton
pushed a commit
to luketainton/repos_pypilot
that referenced
this pull request
Jun 18, 2026
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` |  |  | --- ### 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 <span class="title-ref">--doctest-modules</span>, 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 <span class="title-ref">--report-chars</span> 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 <span class="title-ref">repr</span>. - [#​14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#​14137](pytest-dev/pytest#14137): <span class="title-ref">pytest.ScopeName</span> 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 <span class="title-ref">|</span> (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 <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize. - [#​13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> 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 <span class="title-ref">Config.get\_terminal\_writer</span> 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMjAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIyMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> 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>
luketainton
pushed a commit
to luketainton/repos_epage
that referenced
this pull request
Jun 18, 2026
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` |  |  | --- ### 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 <span class="title-ref">--doctest-modules</span>, 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 <span class="title-ref">--report-chars</span> 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 <span class="title-ref">repr</span>. - [#​14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#​14137](pytest-dev/pytest#14137): <span class="title-ref">pytest.ScopeName</span> 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 <span class="title-ref">|</span> (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 <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize. - [#​13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> 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 <span class="title-ref">Config.get\_terminal\_writer</span> 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMjAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIyMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> 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>
luketainton
pushed a commit
to luketainton/luke_instant-msg-api
that referenced
this pull request
Jun 18, 2026
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` |  |  | --- ### 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 <span class="title-ref">--doctest-modules</span>, 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 <span class="title-ref">--report-chars</span> 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 <span class="title-ref">repr</span>. - [#​14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#​14137](pytest-dev/pytest#14137): <span class="title-ref">pytest.ScopeName</span> 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 <span class="title-ref">|</span> (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 <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize. - [#​13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> 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 <span class="title-ref">Config.get\_terminal\_writer</span> 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMjAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIyMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> 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>
luketainton
pushed a commit
to luketainton/repos_webexmemebot
that referenced
this pull request
Jun 18, 2026
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` |  |  | --- ### 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 <span class="title-ref">--doctest-modules</span>, 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 <span class="title-ref">--report-chars</span> 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 <span class="title-ref">repr</span>. - [#​14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#​14137](pytest-dev/pytest#14137): <span class="title-ref">pytest.ScopeName</span> 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 <span class="title-ref">|</span> (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 <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize. - [#​13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> 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 <span class="title-ref">Config.get\_terminal\_writer</span> 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMjAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIyMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> 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>
luketainton
pushed a commit
to luketainton/repos_roboluke
that referenced
this pull request
Jun 18, 2026
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` |  |  | --- ### 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 <span class="title-ref">--doctest-modules</span>, 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 <span class="title-ref">--report-chars</span> 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 <span class="title-ref">repr</span>. - [#​14026](pytest-dev/pytest#14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#​14137](pytest-dev/pytest#14137): <span class="title-ref">pytest.ScopeName</span> 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 <span class="title-ref">|</span> (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 <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize. - [#​13884](pytest-dev/pytest#13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> 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 <span class="title-ref">Config.get\_terminal\_writer</span> 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMjAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIyMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 5-iteration default was borrowed from the Trio project, where it was determined empirically to handle PyPy's object resurrection behavior: on PyPy, objects like coroutines can survive GC rounds because executing their del can resurrect them.
On CPython, reference counting frees most objects immediately. One GC pass is sufficient to handle reference cycles, as confirmed by all test_unraisableexception tests passing (including the refcycle variants).
Use 1 pass on CPython and retain 5 on PyPy.