Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 3, 2025

This PR contains the following updates:

Package Change Age Confidence
Cython (source) 3.1.6 -> 3.2.0 age confidence
pytest (changelog) 8.3.5 -> 8.4.2 age confidence

Release Notes

cython/cython (Cython)

v3.2.0

Compare Source

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

(Complete changelog for the 3.2.0 release, including pre-releases.)

Features added

  • Builtin exception types are now inferred.
    (Github issue :issue:6908)

  • The list of known, inferred and optimised Python builtins was updated.
    range is now considered a type. ascii, bin, format, hex, oct were added as functions.
    (Github issue :issue:6931)

  • The f-string syntax was extended according to PEP-701.
    (Github issue :issue:5452)

  • t-strings are implemented according to PEP-750. The implementation backports the template classes
    but prefers existing backports if installed separately.
    (Github issue :issue:6811)

  • Unknown return type annotations with -> are no longer rejected but produce warnings.
    This allows better integration with Python type hints that are not always usable for Cython.
    -> None is also allowed now.
    Patch by jpe. (Github issue :issue:6946)

  • The runtime Python dispatch for fused functions is substantially faster.
    (Github issues :issue:1385, :issue:6996)

  • Freelists (via cdef class decorator and for internally used types such as async)
    are now also used in the Limited API and with extension type specs enabled.
    (Github issue :issue:7151)

  • Module imports now quickly check for an already imported module to speed up reimports.
    Patch by Lysandros Nikolaou. (Github issue :issue:7035)

  • Type checks on PEP-604 union types (int | None) are optimised into separate checks.
    (Github issue :issue:6935)

  • Assignments to the PEP-604 union type float | None allow any suitable Python number as input
    and convert it to a Python float automatically.
    (Github issue :issue:5750)

  • Item type inference was improved for looping over literals.
    (Github issue :issue:6912)

  • Looping over literal sequences and strings now uses efficient C array looping if possible.
    (Github issue :issue:6926)

  • Releasing the GIL from an unknown lock state is more efficient.
    (Github issue :issue:6847)

  • cython.critical_section(PyMutex) now works, as with Python objects.
    (Github issue :issue:6847)

  • bool(c_int/float/ptr) avoid passing through Python objects.
    (Github issue :issue:7015)

  • Variables assigned inside of prange loops can now be initialised outside of the loop.
    (Github issue :issue:7178)

  • Unused exceptions in except clauses are detected in some more cases to avoid their normalisation.
    (Github issue :issue:7021)

  • Mixed operations on C integers with Python ints use less code and are more streamlined for Py3.12+.
    (Github issue :issue:7244)

  • Some object constants are now marked as immortal to speed up their reference counting
    in recent CPython versions. This can be configured with the CYTHON_IMMORTAL_CONSTANTS C macro.
    (Github issue :issue:7118)

  • Further improvements were made to reduce the size of the resulting extension modules.
    (Github issue :issue:6983, :issue:7199, :issue:7220, :issue:7238,
    :issue:7255, :issue:7265)

  • Several improvements were made in freethreaded Python code.
    (Github issues :issue:6936, :issue:6939, :issue:6949, :issue:6984,
    :issue:7011, :issue:7066, :issue:7114, :issue:7200)

  • Several improvements were made for the Limited API.
    (Github issues :issue:6959, :issue:6991)

  • Several improvements were made for the GraalPython support.
    Patch by Michael Šimáček. (Github issue :issue:7074)

  • Some GIL-safe C-API wrappers were added to the libc/libcpp declarations.
    (Github issue :issue:6829, :issue:6993)

  • String and number constants use less storage space in the module.
    (Github issues :issue:6971, :issue:6978, :issue:6986)

  • The managed dict/weakref support in CPython 3.12+ is used for internal types
    to benefit from future CPython optimisations here.
    (Github issue :issue:6891)

  • Using NaN as exception return value is supported.
    (Github issues :issue:6900, :issue:6903)

  • Declarations for C++ condition variables were added.
    (Github issue :issue:6836)

  • The annotated source HTML page shows alternating +/− markers to open/close lines.
    Patch by Kamil Monicz. (Github issue :issue:7099)

  • cython --embed gained a new option --embed-modules=… to list further extension modules
    that will be statically linked into the generated extension module, to get them initialised
    on application start.
    (Github issue :issue:2849)

  • The setup.py script of Cython now allows passing the desired Limited API version
    like --cython-limited-api=3.11.
    (Github issue :issue:7228)

  • Unicode 16.0.0 is used to parse identifiers.
    (Github issue :issue:6836)

Bugs fixed

  • Special float exception values could generate invalid C code.
    (Github issues :issue:6900, :issue:6903)

  • References to the Python bool type could generate invalid C code.
    (Github issue :issue:6902)

  • Using cython.pymutex in an extension type declared as public or api
    generated invalid C code missing the required PyMutex declarations.
    (Github issues :issue:6992, :issue:6995)

  • Cython's type sharing across modules suffered from race conditions if multiple modules
    tried to initialise and share their types concurrently. This is due to an underlying
    CPython issue and cannot easily be worked around completely. In the common case that
    module dicts are plain Python dict objects, however, Cython now uses a .setdefault()
    equivalent for thread-safe type sharing.
    See python/cpython#137422
    (Github issue :issue:7076)

  • Cython incorrectly called PyList_GetItemRef() in PyPy and GraalPython before Py3.13.
    (Github issue :issue:7269)

  • Iterating over temporary memoryviews could crash Cython.
    (Github issue :issue:7005)

  • Type casts on constants as part of numeric expressions could crash Cython.
    (Github issue :issue:6779)

  • Long code bodies in with statements could crash Cython.
    (Github issue :issue:7122)

  • Vectorcalls could use needless temp assignments for self.
    (Github issue :issue:6909)

  • Indexing bytes failed to optimise in some cases.
    (Github issue :issue:6997)

  • Optimised C integer formatting in f-strings failed to apply to typedef types.
    (Github issue :issue:7170)

  • In auto-pickling, trying to unpickle an object that has no __dict__ from object pickle data
    that includes instance dict state is now an error.
    (Github issue :issue:7222)

  • The type objects of heap types were not always correctly decrefed on deallocation.
    (Github issue :issue:7145)

  • Pure mode type aliases like p_int or ulong leaked into some C type contexts,
    risking to conflict with user declarations.
    (Github issues :issue:6922, :issue:6339)

  • Boolean (emptyness) tests on builtin containers could fail to handle (unlikely) errors.
    (Github issue :issue:7090)

  • The return type of bytes.join() was sometimes inferred as plain object.
    (Github issue :issue:6987)

  • Type inference could fail to understand prange() arguments.
    (Github issue :issue:6974)

  • embedsignatures failed if lambda was used in function default arguments.
    (Github issue :issue:6880)

  • An internal C function was not marked as static and leaked a linker symbol.
    (Github issue :issue:6957)

  • PyType_FromModuleAndSpec was incorrectly used in Limited API code before Py3.10.
    (Github issue :issue:7181)

  • Conversion code for memoryview dtypes from and to Python objects generated C warnings about
    incorrect const / non-const casting code.
    (Github issue :issue:7219)

  • Cython's tools and frontend scripts now use python3 instead of just python
    in their shebang line.
    Patch by Matti Picus. (Github issue :issue:7053)

  • Extension arguments defined for the shared code module were ignored in cythonize().
    (Github issue :issue:7251)

  • Failures while following package attributes in import pkg.module as … were not handled.

  • Trying to instantiate internal types used by Cython is now prohibited.
    (Github issue :issue:7263)

  • The setup.py script in the Demos/ subdirectory failed to build.
    (Github issue :issue:7228)

  • The cygdb program failed to work with virtualenvs on Windows.
    Patch by Merlin. (Github issue :issue:7268)

  • Includes all fixes as of Cython 3.1.6.

Other changes

  • Some lesser used platforms (Windows ARM/i686, macOS x86_64, Linux i686, musllinux)
    now use Py3.9 abi3 binary wheels instead of Python version specific wheels.
    We also added an abi3 wheel for armv7l.
    (Github issues :issue:7227, :issue:7248, :issue:7250)

  • Usages of Py_TPFLAGS_HAVE_FINALIZE were removed. The constant remains available as cimport from
    cpython.object for legacy reasons.
    (Github issue :issue:6423)

pytest-dev/pytest (pytest)

v8.4.2

Compare Source

pytest 8.4.2 (2025-09-03)

Bug fixes

  • #​13478: Fixed a crash when using console_output_style{.interpreted-text role="confval"} with times and a module is skipped.

  • #​13530: Fixed a crash when using pytest.approx{.interpreted-text role="func"} and decimal.Decimal{.interpreted-text role="class"} instances with the decimal.FloatOperation{.interpreted-text role="class"} trap set.

  • #​13549: No longer evaluate type annotations in Python 3.14 when inspecting function signatures.

    This prevents crashes during module collection when modules do not explicitly use from __future__ import annotations and import types for annotations within a if TYPE_CHECKING: block.

  • #​13559: Added missing [int]{.title-ref} and [float]{.title-ref} variants to the [Literal]{.title-ref} type annotation of the [type]{.title-ref} parameter in pytest.Parser.addini{.interpreted-text role="meth"}.

  • #​13563: pytest.approx{.interpreted-text role="func"} now only imports numpy if NumPy is already in sys.modules. This fixes unconditional import behavior introduced in [8.4.0]{.title-ref}.

Improved documentation

  • #​13577: Clarify that pytest_generate_tests is discovered in test modules/classes; other hooks must be in conftest.py or plugins.

Contributor-facing changes

  • #​13480: Self-testing: fixed a few test failures when run with -Wdefault or a similar override.
  • #​13547: Self-testing: corrected expected message for test_doctest_unexpected_exception in Python 3.14.
  • #​13684: Make pytest's own testsuite insensitive to the presence of the CI environment variable -- by ogrisel{.interpreted-text role="user"}.

v8.4.1

Compare Source

pytest 8.4.1 (2025-06-17)

Bug fixes

  • #​13461: Corrected _pytest.terminal.TerminalReporter.isatty to support
    being called as a method. Before it was just a boolean which could
    break correct code when using -o log_cli=true).

  • #​13477: Reintroduced pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.

    This warning is raised when a test functions returns a value other than None, which is often a mistake made by beginners.

    See return-not-none{.interpreted-text role="ref"} for more information.

  • #​13497: Fixed compatibility with Twisted 25+.

Improved documentation

  • #​13492: Fixed outdated warning about faulthandler not working on Windows.

v8.4.0

Compare Source

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

  • #​11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.

  • #​12346: Tests will now fail, instead of raising a warning, if they return any value other than None.

  • #​12874: We dropped support for Python 3.8 following its end of life (2024-10-07).

  • #​12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

    See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

  • #​10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.

New features

  • #​11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.

  • #​12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.

  • #​12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.

  • #​12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

    This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.

  • #​12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

    For example:

contents of src/domain.py

class Testament: ...

contents of tests/test_testament.py

from domain import Testament

def test_testament(): ...
```

In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.

This behavior can now be prevented by setting the new `collect_imported_tests`{.interpreted-text role="confval"} configuration option to `false`, which will make pytest collect classes/functions from test files **only** if they are defined in that file.

\-- by `FreerGit`{.interpreted-text role="user"}
  • #​12765: Thresholds to trigger snippet truncation can now be set with truncation_limit_lines{.interpreted-text role="confval"} and truncation_limit_chars{.interpreted-text role="confval"}.

    See truncation-params{.interpreted-text role="ref"} for more information.

  • #​13125: console_output_style{.interpreted-text role="confval"} now supports times to show execution time of each test.

  • #​13192: pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string to match, as this will match against any value. Use match="^$" if you want to check that an exception has no message.

  • #​13192: pytest.raises{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has ^ and $ and is otherwise escaped.

  • #​13192: You can now pass with pytest.raises(check=fn): <pytest.raises>{.interpreted-text role="func"}, where fn is a function which takes a raised exception and returns a boolean. The raises fails if no exception was raised (as usual), passes if an exception is raised and fn returns True (as well as match and the type matching, if specified, which are checked before), and propagates the exception if fn returns False (which likely also fails the test).

  • #​13228: hidden-param{.interpreted-text role="ref"} can now be used in id of pytest.param{.interpreted-text role="func"} or in
    ids of Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"}.
    It hides the parameter set from the test name.

  • #​13253: New flag: --disable-plugin-autoload <disable_plugin_autoload>{.interpreted-text role="ref"} which works as an alternative to PYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files with addopts{.interpreted-text role="confval"}.

Improvements in existing functionality

  • #​10224: pytest's short and long traceback styles (how-to-modifying-python-tb-printing{.interpreted-text role="ref"})
    now have partial 657{.interpreted-text role="pep"} support and will show specific code segments in the
    traceback.

    ================================= FAILURES =================================
    _______________________ test_gets_correct_tracebacks _______________________
    
    test_tracebacks.py:12: in test_gets_correct_tracebacks
        assert manhattan_distance(p1, p2) == 1
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
    test_tracebacks.py:6: in manhattan_distance
        return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)
                               ^^^^^^^^^
    E   AttributeError: 'NoneType' object has no attribute 'x'
    

    -- by ammaraskar{.interpreted-text role="user"}

  • #​11118: Now pythonpath{.interpreted-text role="confval"} configures [$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the [-p]{.title-ref} command-line option.

    -- by millerdev{.interpreted-text role="user"}

  • #​11381: The type parameter of the parser.addini method now accepts ["int"]{.title-ref} and "float" parameters, facilitating the parsing of configuration values in the configuration file.

    Example:

    def pytest_addoption(parser):
        parser.addini("int_value", type="int", default=2, help="my int value")
        parser.addini("float_value", type="float", default=4.2, help="my float value")

    The [pytest.ini]{.title-ref} file:

    [pytest]
    int_value = 3
    float_value = 5.4
  • #​11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.

    -- by the-compiler{.interpreted-text role="user"} and glyphack{.interpreted-text role="user"}

  • #​12426: A warning is now issued when pytest.mark.usefixtures ref{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.

  • #​12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.

  • #​12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.

    This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.

  • #​12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.

  • #​12958: A number of unraisable <unraisable>{.interpreted-text role="ref"} enhancements:

    • Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions.
    • Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions.
    • Collect multiple unraisable exceptions per test phase.
    • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
    • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
    • Report the unraisable exception as the cause of the pytest.PytestUnraisableExceptionWarning{.interpreted-text role="class"} exception if raised.
    • Compute the repr of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.
  • #​13010: pytest.approx{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.

  • #​13016: A number of threadexception <unraisable>{.interpreted-text role="ref"} enhancements:

    • Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads.
    • Collect multiple thread exceptions per test phase.
    • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
    • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
    • Report the thread exception as the cause of the pytest.PytestUnhandledThreadExceptionWarning{.interpreted-text role="class"} exception if raised.
    • Extract the name of the thread object in the excepthook which should help with resurrection of the thread.
  • #​13031: An empty parameter set as in pytest.mark.parametrize([], ids=idfunc) will no longer trigger a call to idfunc with internal objects.

  • #​13115: Allows supplying ExceptionGroup[Exception] and BaseExceptionGroup[BaseException] to pytest.raises to keep full typing on ExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"}:

    with pytest.raises(ExceptionGroup[Exception]) as exc_info:
        some_function()

    Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.

  • #​13122: The --stepwise mode received a number of improvements:

    • It no longer forgets the last failed test in case pytest is executed later without the flag.

      This enables the following workflow:

      1. Execute pytest with --stepwise, pytest then stops at the first failing test;
      2. Iteratively update the code and run the test in isolation, without the --stepwise flag (for example in an IDE), until it is fixed.
      3. Execute pytest with --stepwise again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.

      Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.

      This change however might cause issues if the --stepwise mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).

    • New --stepwise-reset/--sw-reset flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.

  • #​13308: Added official support for Python 3.14.

  • #​13380: Fix ExceptionGroup{.interpreted-text role="class"} traceback filtering to exclude pytest internals.

  • #​13415: The author metadata of the BibTex example is now correctly formatted with last names following first names.
    An example of BibLaTex has been added.
    BibTex and BibLaTex examples now clearly indicate that what is cited is software.

    -- by willynilly{.interpreted-text role="user"}

  • #​13420: Improved test collection performance by optimizing path resolution used in FSCollector.

  • #​13457: The error message about duplicate parametrization no longer displays an internal stack trace.

  • #​4112: Using pytest.mark.usefixtures <pytest.mark.usefixtures ref>{.interpreted-text role="ref"} on pytest.param{.interpreted-text role="func"} now produces an error instead of silently doing nothing.

  • #​5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling pytest.main{.interpreted-text role="func"}.

[#&#8203;6985](https://redirect.github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.
:   -   The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.

    -   Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 ± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 ± 1]{.title-ref}).

        Example:

        **Previous Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1.0e+00
        ```

        **Current Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1
        ```

    \-- by `fazeelghafoor`{.interpreted-text role="user"}
  • #​7683: The formerly optional pygments dependency is now required, causing output always to be source-highlighted (unless disabled via the --code-highlight=no CLI option).

Bug fixes

  • #​10404: Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible
    so that warnings as errors are collected throughout the pytest run and before the
    unraisable and threadexcept hooks are removed.

    This allows very late warnings and unraisable/threadexcept exceptions to fail the test suite.

    This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered.

  • #​11067: The test report is now consistent regardless if the test xfailed via pytest.mark.xfail <pytest.mark.xfail ref>{.interpreted-text role="ref"} or pytest.fail{.interpreted-text role="func"}.

    Previously, xfailed tests via the marker would have the string "reason: " prefixed to the message, while those xfailed via the function did not. The prefix has been removed.

  • #​12008: In 11220{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted.

  • #​12863: Fix applying markers, including pytest.mark.parametrize <pytest.mark.parametrize ref>{.interpreted-text role="ref"} when placed above [@​staticmethod]{.title-ref} or [@​classmethod]{.title-ref}.

  • #​12929: Handle StopIteration from test cases, setup and teardown correctly.

  • #​12938: Fixed --durations-min argument not respected if -vv is used.

  • #​12946: Fixed missing help for pdb{.interpreted-text role="mod"} commands wrapped by pytest -- by adamchainz{.interpreted-text role="user"}.

  • #​12981: Prevent exceptions in pytest.Config.add_cleanup{.interpreted-text role="func"} callbacks preventing further cleanups.

  • #​13047: Restore pytest.approx{.interpreted-text role="func"} handling of equality checks between [bool]{.title-ref} and [numpy.bool_]{.title-ref} types.

    Comparing [bool]{.title-ref} and [numpy.bool_]{.title-ref} using pytest.approx{.interpreted-text role="func"} accidentally changed in version [8.3.4]{.title-ref} and [8.3.5]{.title-ref} to no longer match:

    >>> import numpy as np
    >>> from pytest import approx
    >>> [np.True_, np.True_] == pytest.approx([True, True])
    False

    This has now been fixed:

    >>> [np.True_, np.True_] == pytest.approx([True, True])
    True
  • #​13119: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.

  • #​13175: The diff is now also highlighted correctly when comparing two strings.

  • #​13248: Fixed an issue where passing a scope in Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"} with indirect=True
    could result in other fixtures being unable to depend on the parametrized fixture.

  • #​13291: Fixed repr of attrs objects in assertion failure messages when using attrs>=25.2.

  • #​13312: Fixed a possible KeyError crash on PyPy during collection of tests involving higher-scoped parameters.

  • #​13345: Fix type hints for pytest.TestReport.when{.interpreted-text role="attr"} and pytest.TestReport.location{.interpreted-text role="attr"}.

  • #​13377: Fixed handling of test methods with positional-only parameter syntax.

    Now, methods are supported that formally define self as positional-only
    and/or fixture parameters as keyword-only, e.g.:

    class TestClass:
    
        def test_method(self, /, *, fixture): ...

    Before, this caused an internal error in pytest.

  • #​13384: Fixed an issue where pytest could report negative durations.

  • #​13420: Added lru_cache to nodes._check_initialpaths_for_relpath.

  • #​9037: Honor disable_test_id_escaping_and_forfeit_all_rights_to_community_support{.interpreted-text role="confval"} when escaping ids in parametrized tests.

Improved documentation

  • #​12535: [This
    example]{.title-ref}<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures>
    showed print statements that do not exactly reflect what the
    different branches actually do. The fix makes the example more precise.

  • #​13218: Pointed out in the pytest.approx{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one.

  • #​13221: Improved grouping of CLI options in the --help output.

  • #​6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the api-reference{.interpreted-text role="ref"} documentation page.

  • #​8612: Add a recipe for handling abstract test classes in the documentation.

    A new example has been added to the documentation to demonstrate how to use a mixin class to handle abstract
    test classes without manually setting the __test__ attribute for subclasses.
    This ensures that subclasses of abstract test classes are automatically collected by pytest.

Packaging updates and notes for downstreams

  • #​13317: Specified minimum allowed versions of colorama, iniconfig,
    and packaging; and bumped the minimum allowed version
    of exceptiongroup for python_version<'3.11' from a release
    candidate to a full release.

Contributor-facing changes

  • #​12017: Mixed internal improvements:

    • Migrate formatting to f-strings in some tests.
    • Use type-safe constructs in JUnitXML tests.
    • MovedMockTiming into _pytest.timing.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

  • #​12647: Fixed running the test suite with the hypothesis pytest plugin.

Miscellaneous internal changes

  • #​6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the public pytest API, as it is part of the signature of the pytest_terminal_summary{.interpreted-text role="hook"} hook.

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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


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

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

@renovate renovate bot added the dependencies label Nov 3, 2025
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 9fcecdf to 500e498 Compare November 5, 2025 17:07
@renovate renovate bot changed the title ⬆️ deps: Update dependency pytest to v8.4.2 ⬆️ deps: Update dependencies (non-major) Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant