Pin pytest to latest version 9.0.3 by pyup-bot · Pull Request #563 · salimfadhley/dockerized_python_playground

pyup-bot · 2026-04-08T13:04:46Z

This PR pins pytest to the latest release 9.0.3.

Changelog

9.0.3

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

Bug fixes
---------

- `12444 &lt;https://github.com/pytest-dev/pytest/issues/12444&gt;`_: Fixed :func:`pytest.approx` which now correctly takes into account :class:`~collections.abc.Mapping` keys order to compare them.


- `13634 &lt;https://github.com/pytest-dev/pytest/issues/13634&gt;`_: Blocking a ``conftest.py`` file using the ``-p no:`` option is now explicitly disallowed.

Previously this resulted in an internal assertion failure during plugin loading.

Pytest now raises a clear ``UsageError`` explaining that conftest files are not plugins and cannot be disabled via ``-p``.


- `13734 &lt;https://github.com/pytest-dev/pytest/issues/13734&gt;`_: Fixed crash when a test raises an exceptiongroup with ``__tracebackhide__ = True``.


- `14195 &lt;https://github.com/pytest-dev/pytest/issues/14195&gt;`_: Fixed an issue where non-string messages passed to `unittest.TestCase.subTest()` were not printed.


- `14343 &lt;https://github.com/pytest-dev/pytest/issues/14343&gt;`_: Fixed use of insecure temporary directory (CVE-2025-71176).



Improved documentation
----------------------

- `13388 &lt;https://github.com/pytest-dev/pytest/issues/13388&gt;`_: Clarified documentation for ``-p`` vs ``PYTEST_PLUGINS`` plugin loading and fixed an incorrect ``-p`` example.


- `13731 &lt;https://github.com/pytest-dev/pytest/issues/13731&gt;`_: Clarified that capture fixtures (e.g. ``capsys`` and ``capfd``) take precedence over the ``-s`` / ``--capture=no`` command-line options in :ref:`Accessing captured output from a test function &lt;accessing-captured-output&gt;`.


- `14088 &lt;https://github.com/pytest-dev/pytest/issues/14088&gt;`_: Clarified that the default :hook:`pytest_collection` hook sets ``session.items`` before it calls :hook:`pytest_collection_finish`, not after.


- `14255 &lt;https://github.com/pytest-dev/pytest/issues/14255&gt;`_: TOML integer log levels must be quoted: Updating reference documentation.



Contributor-facing changes
--------------------------

- `12689 &lt;https://github.com/pytest-dev/pytest/issues/12689&gt;`_: The test reports are now published to Codecov from GitHub Actions.
The test statistics is visible `on the web interface
&lt;https://app.codecov.io/gh/pytest-dev/pytest/tests&gt;`__.

-- by :user:`aleguy02`

9.0.2

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

Bug fixes
---------

- `13896 &lt;https://github.com/pytest-dev/pytest/issues/13896&gt;`_: The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.

You may enable it again by passing ``-p terminalprogress``. We may enable it by default again once compatibility improves in the future.

Additionally, when the environment variable ``TERM`` is ``dumb``, the escape codes are no longer emitted, even if the plugin is enabled.


- `13904 &lt;https://github.com/pytest-dev/pytest/issues/13904&gt;`_: Fixed the TOML type of the :confval:`tmp_path_retention_count` settings in the API reference from number to string.


- `13946 &lt;https://github.com/pytest-dev/pytest/issues/13946&gt;`_: The private ``config.inicfg`` attribute was changed in a breaking manner in pytest 9.0.0.
Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
It will be deprecated in pytest 9.1 and removed in pytest 10.


- `13965 &lt;https://github.com/pytest-dev/pytest/issues/13965&gt;`_: Fixed quadratic-time behavior when handling ``unittest`` subtests in Python 3.10.



Improved documentation
----------------------

- `4492 &lt;https://github.com/pytest-dev/pytest/issues/4492&gt;`_: The API Reference now contains cross-reference-able documentation of :ref:`pytest&#x27;s command-line flags &lt;command-line-flags&gt;`.

9.0.1

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

Bug fixes
---------

- `13895 &lt;https://github.com/pytest-dev/pytest/issues/13895&gt;`_: Restore support for skipping tests via ``raise unittest.SkipTest``.


- `13896 &lt;https://github.com/pytest-dev/pytest/issues/13896&gt;`_: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.


- `13904 &lt;https://github.com/pytest-dev/pytest/issues/13904&gt;`_: Fixed the TOML type of the verbosity settings in the API reference from number to string.


- `13910 &lt;https://github.com/pytest-dev/pytest/issues/13910&gt;`_: Fixed `UserWarning: Do not expect file_or_dir` on some earlier Python 3.12 and 3.13 point versions.



Packaging updates and notes for downstreams
-------------------------------------------

- `13933 &lt;https://github.com/pytest-dev/pytest/issues/13933&gt;`_: The tox configuration has been adjusted to make sure the desired
version string can be passed into its :ref:`package_env` through
the ``SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`` environment
variable as a part of the release process -- by :user:`webknjaz`.



Contributor-facing changes
--------------------------

- `13891 &lt;https://github.com/pytest-dev/pytest/issues/13891&gt;`_, `#13942 &lt;https://github.com/pytest-dev/pytest/issues/13942&gt;`_: The CI/CD part of the release automation is now capable of
creating GitHub Releases without having a Git checkout on
disk -- by :user:`bluetech` and :user:`webknjaz`.


- `13933 &lt;https://github.com/pytest-dev/pytest/issues/13933&gt;`_: The tox configuration has been adjusted to make sure the desired
version string can be passed into its :ref:`package_env` through
the ``SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`` environment
variable as a part of the release process -- by :user:`webknjaz`.

9.0.0

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

New features
------------


- `1367 &lt;https://github.com/pytest-dev/pytest/issues/1367&gt;`_: **Support for subtests** has been added.

:ref:`subtests &lt;subtests&gt;` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

Example:

.. code-block:: python

   def contains_docstring(p: Path) -&gt; bool:
       &quot;&quot;&quot;Return True if the given Python file contains a top-level docstring.&quot;&quot;&quot;
       ...


   def test_py_files_contain_docstring(subtests: pytest.Subtests) -&gt; None:
       for path in Path.cwd().glob(&quot;*.py&quot;):
           with subtests.test(path=str(path)):
               assert contains_docstring(path)


Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

In addition, :meth:`unittest.TestCase.subTest` is now also supported.

This feature was originally implemented as a separate plugin in `pytest-subtests &lt;https://github.com/pytest-dev/pytest-subtests&gt;`__, but since then has been merged into the core.

.. note::

   This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.


- `13743 &lt;https://github.com/pytest-dev/pytest/issues/13743&gt;`_: Added support for **native TOML configuration files**.

While pytest, since version 6, supports configuration in ``pyproject.toml`` files under ``[tool.pytest.ini_options]``,
it does so in an &quot;INI compatibility mode&quot;, where all configuration values are treated as strings or list of strings.
Now, pytest supports the native TOML data model.

In ``pyproject.toml``, the native TOML configuration is under the ``[tool.pytest]`` table.

.. code-block:: toml

    pyproject.toml
   [tool.pytest]
   minversion = &quot;9.0&quot;
   addopts = [&quot;-ra&quot;, &quot;-q&quot;]
   testpaths = [
       &quot;tests&quot;,
       &quot;integration&quot;,
   ]

The ``[tool.pytest.ini_options]`` table remains supported, but both tables cannot be used at the same time.

If you prefer to use a separate configuration file, or don&#x27;t use ``pyproject.toml``, you can use ``pytest.toml`` or ``.pytest.toml``:

.. code-block:: toml

    pytest.toml or .pytest.toml
   [pytest]
   minversion = &quot;9.0&quot;
   addopts = [&quot;-ra&quot;, &quot;-q&quot;]
   testpaths = [
       &quot;tests&quot;,
       &quot;integration&quot;,
   ]

The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

See :ref:`config file formats` for full details.


- `13823 &lt;https://github.com/pytest-dev/pytest/issues/13823&gt;`_: Added a **&quot;strict mode&quot;** enabled by the :confval:`strict` configuration option.

When set to ``true``, the :confval:`strict` option currently enables

* :confval:`strict_config`
* :confval:`strict_markers`
* :confval:`strict_parametrization_ids`
* :confval:`strict_xfail`

The individual strictness options can be explicitly set to override the global :confval:`strict` setting.

The previously-deprecated ``--strict`` command-line flag now enables strict mode.

If pytest adds new strictness options in the future, they will also be enabled in strict mode.
Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
or if you want to proactively adopt new strictness options as they are added.

See :ref:`strict mode` for more details.


- `13737 &lt;https://github.com/pytest-dev/pytest/issues/13737&gt;`_: Added the :confval:`strict_parametrization_ids` configuration option.

When set, pytest emits an error if it detects non-unique parameter set IDs,
rather than automatically making the IDs unique by adding `0`, `1`, ... to them.
This can be particularly useful for catching unintended duplicates.


- `13072 &lt;https://github.com/pytest-dev/pytest/issues/13072&gt;`_: Added support for displaying test session **progress in the terminal tab** using the `OSC 9;4; &lt;https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC&gt;`_ ANSI sequence.

**Note**: *This feature has been disabled by default in version 9.0.2, except on Windows, due to compatibility issues with some terminal emulators.
You may enable it again by passing* ``-p terminalprogress``. *We may enable it by default again once compatibility improves in the future.*

When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
you&#x27;ll see the progress in the terminal tab or window,
allowing you to monitor pytest&#x27;s progress at a glance.

This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:
- On a user level, using ``-p no:terminalprogress`` on the command line or via an environment variable ``PYTEST_ADDOPTS=&#x27;-p no:terminalprogress&#x27;``.
- On a project configuration level, using ``addopts = &quot;-p no:terminalprogress&quot;``.


- `478 &lt;https://github.com/pytest-dev/pytest/issues/478&gt;`_: Support PEP420 (implicit namespace packages) as `--pyargs` target when :confval:`consider_namespace_packages` is `true` in the config.

Previously, this option only impacted package imports, now it also impacts tests discovery.


- `13678 &lt;https://github.com/pytest-dev/pytest/issues/13678&gt;`_: Added a new :confval:`faulthandler_exit_on_timeout` configuration option set to &quot;false&quot; by default to let `faulthandler` interrupt the `pytest` process after a timeout in case of deadlock.

Previously, a `faulthandler` timeout would only dump the traceback of all threads to stderr, but would not interrupt the `pytest` process.

-- by :user:`ogrisel`.


- `13829 &lt;https://github.com/pytest-dev/pytest/issues/13829&gt;`_: Added support for configuration option aliases via the ``aliases`` parameter in :meth:`Parser.addini() &lt;pytest.Parser.addini&gt;`.

Plugins can now register alternative names for configuration options,
allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.



Improvements in existing functionality
--------------------------------------

- `13330 &lt;https://github.com/pytest-dev/pytest/issues/13330&gt;`_: Having pytest configuration spread over more than one file (for example having both a ``pytest.ini`` file and ``pyproject.toml`` with a ``[tool.pytest.ini_options]`` table) will now print a warning to make it clearer to the user that only one of them is actually used.

-- by :user:`sgaist`


- `13574 &lt;https://github.com/pytest-dev/pytest/issues/13574&gt;`_: The single argument ``--version`` no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

Passing ``--version`` twice (e.g., ``pytest --version --version``) retains the original behavior, showing both the pytest version and plugin information.

.. note::

   Since ``--version`` is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as :envvar:`PYTEST_ADDOPTS` or :confval:`addopts`.


- `13823 &lt;https://github.com/pytest-dev/pytest/issues/13823&gt;`_: Added :confval:`strict_xfail` as an alias to the ``xfail_strict`` option,
:confval:`strict_config` as an alias to the ``--strict-config`` flag,
and :confval:`strict_markers` as an alias to the ``--strict-markers`` flag.
This makes all strictness options consistently have configuration options with the prefix ``strict_``.

- `13700 &lt;https://github.com/pytest-dev/pytest/issues/13700&gt;`_: `--junitxml`  no longer prints the `generated xml file` summary at the end of the pytest session when `--quiet` is given.


- `13732 &lt;https://github.com/pytest-dev/pytest/issues/13732&gt;`_: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.


- `13859 &lt;https://github.com/pytest-dev/pytest/issues/13859&gt;`_: Clarify the error message for `pytest.raises()` when a regex `match` fails.


- `13861 &lt;https://github.com/pytest-dev/pytest/issues/13861&gt;`_: Better sentence structure in a test&#x27;s expected error message. Previously, the error message would be &quot;expected exception must be &lt;expected&gt;, but got &lt;actual&gt;&quot;. Now, it is &quot;Expected &lt;expected&gt;, but got &lt;actual&gt;&quot;.


Removals and backward incompatible breaking changes
---------------------------------------------------

- `12083 &lt;https://github.com/pytest-dev/pytest/issues/12083&gt;`_: Fixed a bug where an invocation such as `pytest a/ a/b` would cause only tests from `a/b` to run, and not other tests under `a/`.

The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

1. `pytest a/b a/` or `pytest a/ a/b` are equivalent to `pytest a`; if an argument overlaps another arguments, only the prefix remains.

2. `pytest x.py x.py` is equivalent to `pytest x.py`; previously such an invocation was taken as an explicit request to run the tests from the file twice.

If you rely on these behaviors, consider using :ref:`--keep-duplicates &lt;duplicate-paths&gt;`, which retains its existing behavior (including the bug).


- `13719 &lt;https://github.com/pytest-dev/pytest/issues/13719&gt;`_: Support for Python 3.9 is dropped following its end of life.


- `13766 &lt;https://github.com/pytest-dev/pytest/issues/13766&gt;`_: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables `$CI` or `$BUILD_NUMBER` was defined;
now, CI mode is only activated if at least one of those variables is defined and set to a *non-empty* value.


- The non-public ``config.args`` attribute used to be able to contain ``pathlib.Path`` instances; now it can only contain strings.


- `13779 &lt;https://github.com/pytest-dev/pytest/issues/13779&gt;`_: **PytestRemovedIn9Warning deprecation warnings are now errors by default.**

Following our plan to remove deprecated features with as little disruption as
possible, all warnings of type ``PytestRemovedIn9Warning`` now generate errors
instead of warning messages by default.

**The affected features will be effectively removed in pytest 9.1**, so please consult the
:ref:`deprecations` section in the docs for directions on how to update existing code.

In the pytest ``9.0.X`` series, it is possible to change the errors back into warnings as a
stopgap measure by adding this to your ``pytest.ini`` file:

.. code-block:: ini

   [pytest]
   filterwarnings =
       ignore::pytest.PytestRemovedIn9Warning

But this will stop working when pytest ``9.1`` is released.

**If you have concerns** about the removal of a specific feature, please add a
comment to :issue:`13779`.



Deprecations (removal in next major release)
--------------------------------------------

- `13807 &lt;https://github.com/pytest-dev/pytest/issues/13807&gt;`_: :meth:`monkeypatch.syspath_prepend() &lt;pytest.MonkeyPatch.syspath_prepend&gt;` now issues a deprecation warning when the prepended path contains legacy namespace packages (those using ``pkg_resources.declare_namespace()``).
Users should migrate to native namespace packages (:pep:`420`).
See :ref:`monkeypatch-fixup-namespace-packages` for details.


Bug fixes
---------

- `13445 &lt;https://github.com/pytest-dev/pytest/issues/13445&gt;`_: Made the type annotations of :func:`pytest.skip` and friends more spec-complaint to have them work across more type checkers.


- `13537 &lt;https://github.com/pytest-dev/pytest/issues/13537&gt;`_: Fixed a bug in which :class:`ExceptionGroup` with only ``Skipped`` exceptions in teardown was not handled correctly and showed as error.


- `13598 &lt;https://github.com/pytest-dev/pytest/issues/13598&gt;`_: Fixed possible collection confusion on Windows when short paths and symlinks are involved.


- `13716 &lt;https://github.com/pytest-dev/pytest/issues/13716&gt;`_: Fixed a bug where a nonsensical invocation like ``pytest x.py[a]`` (a file cannot be parametrized) was silently treated as ``pytest x.py``. This is now a usage error.


- `13722 &lt;https://github.com/pytest-dev/pytest/issues/13722&gt;`_: Fixed a misleading assertion failure message when using :func:`pytest.approx` on mappings with differing lengths.


- `13773 &lt;https://github.com/pytest-dev/pytest/issues/13773&gt;`_: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.


- `13816 &lt;https://github.com/pytest-dev/pytest/issues/13816&gt;`_: Fixed :func:`pytest.approx` which now returns a clearer error message when comparing mappings with different keys.


- `13849 &lt;https://github.com/pytest-dev/pytest/issues/13849&gt;`_: Hidden ``.pytest.ini`` files are now picked up as the config file even if empty.
This was an inconsistency with non-hidden ``pytest.ini``.


- `13865 &lt;https://github.com/pytest-dev/pytest/issues/13865&gt;`_: Fixed `--show-capture` with `--tb=line`.


- `13522 &lt;https://github.com/pytest-dev/pytest/issues/13522&gt;`_: Fixed :fixture:`pytester` in subprocess mode ignored all :attr:`pytester.plugins &lt;pytest.Pytester.plugins&gt;` except the first.

Fixed :fixture:`pytester` in subprocess mode silently ignored non-str :attr:`pytester.plugins &lt;pytest.Pytester.plugins&gt;`.
Now it errors instead.
If you are affected by this, specify the plugin by name, or switch the affected tests to use :func:`pytester.runpytest_inprocess &lt;pytest.Pytester.runpytest_inprocess&gt;` explicitly instead.



Packaging updates and notes for downstreams
-------------------------------------------

- `13791 &lt;https://github.com/pytest-dev/pytest/issues/13791&gt;`_: Minimum requirements on ``iniconfig`` and ``packaging`` were bumped to ``1.0.1`` and ``22.0.0``, respectively.



Contributor-facing changes
--------------------------

- `12244 &lt;https://github.com/pytest-dev/pytest/issues/12244&gt;`_: Fixed self-test failures when `TERM=dumb`.


- `12474 &lt;https://github.com/pytest-dev/pytest/issues/12474&gt;`_: Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.


- `13621 &lt;https://github.com/pytest-dev/pytest/issues/13621&gt;`_: pytest&#x27;s own testsuite now handles the ``lsof`` command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds.


- `13638 &lt;https://github.com/pytest-dev/pytest/issues/13638&gt;`_: Fixed deprecated :command:`gh pr new` command in :file:`scripts/prepare-release-pr.py`.
The script now uses :command:`gh pr create` which is compatible with GitHub CLI v2.0+.


- `13695 &lt;https://github.com/pytest-dev/pytest/issues/13695&gt;`_: Flush `stdout` and `stderr` in `Pytester.run` to avoid truncated outputs in `test_faulthandler.py::test_timeout` on CI -- by :user:`ogrisel`.


- `13771 &lt;https://github.com/pytest-dev/pytest/issues/13771&gt;`_: Skip `test_do_not_collect_symlink_siblings` on Windows environments without symlink support to avoid false negatives.


- `13841 &lt;https://github.com/pytest-dev/pytest/issues/13841&gt;`_: ``tox&gt;=4`` is now required when contributing to pytest.

- `13625 &lt;https://github.com/pytest-dev/pytest/issues/13625&gt;`_: Added missing docstrings to ``pytest_addoption()``, ``pytest_configure()``, and ``cacheshow()`` functions in ``cacheprovider.py``.



Miscellaneous internal changes
------------------------------

- `13830 &lt;https://github.com/pytest-dev/pytest/issues/13830&gt;`_: Configuration overrides (``-o``/``--override-ini``) are now processed during startup rather than during :func:`config.getini() &lt;pytest.Config.getini&gt;`.

8.4.2

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

Bug fixes
---------

- `13478 &lt;https://github.com/pytest-dev/pytest/issues/13478&gt;`_: Fixed a crash when using :confval:`console_output_style` with ``times`` and a module is skipped.


- `13530 &lt;https://github.com/pytest-dev/pytest/issues/13530&gt;`_: Fixed a crash when using :func:`pytest.approx` and :class:`decimal.Decimal` instances with the :class:`decimal.FloatOperation` trap set.


- `13549 &lt;https://github.com/pytest-dev/pytest/issues/13549&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/13559&gt;`_: Added missing `int` and `float` variants to the `Literal` type annotation of the `type` parameter in :meth:`pytest.Parser.addini`.


- `13563 &lt;https://github.com/pytest-dev/pytest/issues/13563&gt;`_: :func:`pytest.approx` now only imports ``numpy`` if NumPy is already in ``sys.modules``. This fixes unconditional import behavior introduced in `8.4.0`.



Improved documentation
----------------------

- `13577 &lt;https://github.com/pytest-dev/pytest/issues/13577&gt;`_: Clarify that ``pytest_generate_tests`` is discovered in test modules/classes; other hooks must be in ``conftest.py`` or plugins.



Contributor-facing changes
--------------------------

- `13480 &lt;https://github.com/pytest-dev/pytest/issues/13480&gt;`_: Self-testing: fixed a few test failures when run with ``-Wdefault`` or a similar override.


- `13547 &lt;https://github.com/pytest-dev/pytest/issues/13547&gt;`_: Self-testing: corrected expected message for ``test_doctest_unexpected_exception`` in Python ``3.14``.


- `13684 &lt;https://github.com/pytest-dev/pytest/issues/13684&gt;`_: Make pytest&#x27;s own testsuite insensitive to the presence of the ``CI`` environment variable -- by :user:`ogrisel`.

8.4.1

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

Bug fixes
---------

- `13461 &lt;https://github.com/pytest-dev/pytest/issues/13461&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/13477&gt;`_: Reintroduced :class:`pytest.PytestReturnNotNoneWarning` which was removed by accident in pytest `8.4`.

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

See :ref:`return-not-none` for more information.


- `13497 &lt;https://github.com/pytest-dev/pytest/issues/13497&gt;`_: Fixed compatibility with ``Twisted 25+``.



Improved documentation
----------------------

- `13492 &lt;https://github.com/pytest-dev/pytest/issues/13492&gt;`_: Fixed outdated warning about ``faulthandler`` not working on Windows.

8.4.0

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

Removals and backward incompatible breaking changes
---------------------------------------------------

- `11372 &lt;https://github.com/pytest-dev/pytest/issues/11372&gt;`_: Async tests will now fail, instead of warning+skipping, if you don&#x27;t have any suitable plugin installed.


- `12346 &lt;https://github.com/pytest-dev/pytest/issues/12346&gt;`_: Tests will now fail, instead of raising a warning, if they return any value other than None.


- `12874 &lt;https://github.com/pytest-dev/pytest/issues/12874&gt;`_: We dropped support for Python 3.8 following its end of life (2024-10-07).


- `12960 &lt;https://github.com/pytest-dev/pytest/issues/12960&gt;`_: 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 :ref:`the docs &lt;yield tests deprecated&gt;` for more information.



Deprecations (removal in next major release)
--------------------------------------------

- `10839 &lt;https://github.com/pytest-dev/pytest/issues/10839&gt;`_: Requesting an asynchronous fixture without a `pytest_fixture_setup` 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 :ref:`sync-test-async-fixture`.



New features
------------

- `11538 &lt;https://github.com/pytest-dev/pytest/issues/11538&gt;`_: Added :class:`pytest.RaisesGroup` as an equivalent to :func:`pytest.raises` for expecting :exc:`ExceptionGroup`. Also adds :class:`pytest.RaisesExc` which is now the logic behind :func:`pytest.raises` and used as parameter to :class:`pytest.RaisesGroup`. ``RaisesGroup`` includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating :ref:`except* &lt;except_star&gt;`. See :ref:`assert-matching-exception-groups` and docstrings for more information.


- `12081 &lt;https://github.com/pytest-dev/pytest/issues/12081&gt;`_: Added :fixture:`capteesys` to capture AND pass output to next handler set by ``--capture=``.


- `12504 &lt;https://github.com/pytest-dev/pytest/issues/12504&gt;`_: :func:`pytest.mark.xfail` now accepts :class:`pytest.RaisesGroup` for the ``raises`` parameter when you expect an exception group. You can also pass a :class:`pytest.RaisesExc` if you e.g. want to make use of the ``check`` parameter.


- `12713 &lt;https://github.com/pytest-dev/pytest/issues/12713&gt;`_: New `--force-short-summary` 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 &lt;https://github.com/pytest-dev/pytest/issues/12749&gt;`_: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

For example:

.. code-block:: python

    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` from `tests/test_testament.py` because it starts with `Test`, 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 :confval:`collect_imported_tests` configuration option to ``false``, which will make pytest collect classes/functions from test files **only** if they are defined in that file.

-- by :user:`FreerGit`


- `12765 &lt;https://github.com/pytest-dev/pytest/issues/12765&gt;`_: Thresholds to trigger snippet truncation can now be set with :confval:`truncation_limit_lines` and :confval:`truncation_limit_chars`.

See :ref:`truncation-params` for more information.


- `13125 &lt;https://github.com/pytest-dev/pytest/issues/13125&gt;`_: :confval:`console_output_style` now supports ``times`` to show execution time of each test.


- `13192 &lt;https://github.com/pytest-dev/pytest/issues/13192&gt;`_: :func:`pytest.raises` will now raise a warning when passing an empty string to ``match``, as this will match against any value. Use ``match=&quot;^$&quot;`` if you want to check that an exception has no message.


- `13192 &lt;https://github.com/pytest-dev/pytest/issues/13192&gt;`_: :func:`pytest.raises` will now print a helpful string diff if matching fails and the match parameter has ``^`` and ``$`` and is otherwise escaped.


- `13192 &lt;https://github.com/pytest-dev/pytest/issues/13192&gt;`_: You can now pass :func:`with pytest.raises(check=fn): &lt;pytest.raises&gt;`, 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 &lt;https://github.com/pytest-dev/pytest/issues/13228&gt;`_: :ref:`hidden-param` can now be used in ``id`` of :func:`pytest.param` or in
``ids`` of :py:func:`Metafunc.parametrize &lt;pytest.Metafunc.parametrize&gt;`.
It hides the parameter set from the test name.


- `13253 &lt;https://github.com/pytest-dev/pytest/issues/13253&gt;`_: New flag: :ref:`--disable-plugin-autoload &lt;disable_plugin_autoload&gt;` which works as an alternative to :envvar:`PYTEST_DISABLE_PLUGIN_AUTOLOAD` when setting environment variables is inconvenient; and allows setting it in config files with :confval:`addopts`.



Improvements in existing functionality
--------------------------------------

- `10224 &lt;https://github.com/pytest-dev/pytest/issues/10224&gt;`_: pytest&#x27;s ``short`` and ``long`` traceback styles (:ref:`how-to-modifying-python-tb-printing`)
now have partial :pep:`657` support and will show specific code segments in the
traceback.

.. code-block:: pytest

   ================================= 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: &#x27;NoneType&#x27; object has no attribute &#x27;x&#x27;

-- by :user:`ammaraskar`


- `11118 &lt;https://github.com/pytest-dev/pytest/issues/11118&gt;`_: Now :confval:`pythonpath` configures `$PYTHONPATH` earlier than before during the initialization process, which now also affects plugins loaded via the `-p` command-line option.

-- by :user:`millerdev`


- `11381 &lt;https://github.com/pytest-dev/pytest/issues/11381&gt;`_: The ``type`` parameter of the ``parser.addini`` method now accepts `&quot;int&quot;` and ``&quot;float&quot;`` parameters, facilitating the parsing of configuration values in the configuration file.

Example:

.. code-block:: python

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

The `pytest.ini` file:

.. code-block:: ini

 [pytest]
 int_value = 3
 float_value = 5.4


- `11525 &lt;https://github.com/pytest-dev/pytest/issues/11525&gt;`_: Fixtures are now clearly represented in the output as a &quot;fixture object&quot;, 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 :user:`the-compiler` and :user:`glyphack`


- `12426 &lt;https://github.com/pytest-dev/pytest/issues/12426&gt;`_: A warning is now issued when :ref:`pytest.mark.usefixtures ref` is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.


- `12707 &lt;https://github.com/pytest-dev/pytest/issues/12707&gt;`_: Exception chains can be navigated when dropped into Pdb in Python 3.13+.


- `12736 &lt;https://github.com/pytest-dev/pytest/issues/12736&gt;`_: Added a new attribute `name` with the fixed value `&quot;pytest tests&quot;` to the root tag `testsuites` 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` specification that pytest&#x27;s implementation is based on.


- `12943 &lt;https://github.com/pytest-dev/pytest/issues/12943&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/12958&gt;`_: A number of :ref:`unraisable &lt;unraisable&gt;` 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 :mod:`tracemalloc` allocation traceback (if available).
* Avoid using a generator based hook to allow handling :class:`StopIteration` in test failures.
* Report the unraisable exception as the cause of the :class:`pytest.PytestUnraisableExceptionWarning` 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 &lt;https://github.com/pytest-dev/pytest/issues/13010&gt;`_: :func:`pytest.approx` now can compare collections that contain numbers and non-numbers mixed.


- `13016 &lt;https://github.com/pytest-dev/pytest/issues/13016&gt;`_: A number of :ref:`threadexception &lt;unraisable&gt;` 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 :mod:`tracemalloc` allocation traceback (if available).
* Avoid using a generator based hook to allow handling :class:`StopIteration` in test failures.
* Report the thread exception as the cause of the :class:`pytest.PytestUnhandledThreadExceptionWarning` exception if raised.
* Extract the ``name`` of the thread object in the excepthook which should help with resurrection of the thread.


- `13031 &lt;https://github.com/pytest-dev/pytest/issues/13031&gt;`_: An empty parameter set as in ``pytest.mark.parametrize([], ids=idfunc)`` will no longer trigger a call to ``idfunc`` with internal objects.


- `13115 &lt;https://github.com/pytest-dev/pytest/issues/13115&gt;`_: Allows supplying ``ExceptionGroup[Exception]`` and ``BaseExceptionGroup[BaseException]`` to ``pytest.raises`` to keep full typing on :class:`ExceptionInfo &lt;pytest.ExceptionInfo&gt;`:

.. code-block:: python

   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 &lt;https://github.com/pytest-dev/pytest/issues/13122&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/13308&gt;`_: Added official support for Python 3.14.


- `13380 &lt;https://github.com/pytest-dev/pytest/issues/13380&gt;`_: Fix :class:`ExceptionGroup` traceback filtering to exclude pytest internals.


- `13415 &lt;https://github.com/pytest-dev/pytest/issues/13415&gt;`_: 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 :user:`willynilly`


- `13420 &lt;https://github.com/pytest-dev/pytest/issues/13420&gt;`_: Improved test collection performance by optimizing path resolution used in ``FSCollector``.


- `13457 &lt;https://github.com/pytest-dev/pytest/issues/13457&gt;`_: The error message about duplicate parametrization no longer displays an internal stack trace.


- `4112 &lt;https://github.com/pytest-dev/pytest/issues/4112&gt;`_: Using :ref:`pytest.mark.usefixtures &lt;pytest.mark.usefixtures ref&gt;` on :func:`pytest.param` now produces an error instead of silently doing nothing.


- `5473 &lt;https://github.com/pytest-dev/pytest/issues/5473&gt;`_: Replace `:` with `;` in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling :func:`pytest.main`.


- `6985 &lt;https://github.com/pytest-dev/pytest/issues/6985&gt;`_: Improved :func:`pytest.approx` to enhance the readability of value ranges and tolerances between 0.001 and 1000.
 * The `repr` 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`). The updated method now presents the tolerance as a decimal for better readability (e.g., `42 ± 1`).

   Example:

   **Previous Output:**

   .. code-block:: console

       &gt;&gt;&gt; pytest.approx(42, abs=1)
       42 ± 1.0e+00

   **Current Output:**

   .. code-block:: console

       &gt;&gt;&gt; pytest.approx(42, abs=1)
       42 ± 1

 -- by :user:`fazeelghafoor`


- `7683 &lt;https://github.com/pytest-dev/pytest/issues/7683&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/10404&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/11067&gt;`_: The test report is now consistent regardless if the test xfailed via :ref:`pytest.mark.xfail &lt;pytest.mark.xfail ref&gt;` or :func:`pytest.fail`.

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


- `12008 &lt;https://github.com/pytest-dev/pytest/issues/12008&gt;`_: In :pr:`11220`, 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&#x27;s callspecs were assigned after all parametrizations took place. Now, that change is reverted.


- `12863 &lt;https://github.com/pytest-dev/pytest/issues/12863&gt;`_: Fix applying markers, including :ref:`pytest.mark.parametrize &lt;pytest.mark.parametrize ref&gt;` when placed above `staticmethod` or `classmethod`.


- `12929 &lt;https://github.com/pytest-dev/pytest/issues/12929&gt;`_: Handle StopIteration from test cases, setup and teardown correctly.


- `12938 &lt;https://github.com/pytest-dev/pytest/issues/12938&gt;`_: Fixed ``--durations-min`` argument not respected if ``-vv`` is used.


- `12946 &lt;https://github.com/pytest-dev/pytest/issues/12946&gt;`_: Fixed missing help for :mod:`pdb` commands wrapped by pytest -- by :user:`adamchainz`.


- `12981 &lt;https://github.com/pytest-dev/pytest/issues/12981&gt;`_: Prevent exceptions in :func:`pytest.Config.add_cleanup` callbacks preventing further cleanups.


- `13047 &lt;https://github.com/pytest-dev/pytest/issues/13047&gt;`_: Restore :func:`pytest.approx` handling of equality checks between `bool` and `numpy.bool_` types.

Comparing `bool` and `numpy.bool_` using :func:`pytest.approx` accidentally changed in version `8.3.4` and `8.3.5` to no longer match:

.. code-block:: pycon

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

This has now been fixed:

.. code-block:: pycon

   &gt;&gt;&gt; [np.True_, np.True_] == pytest.approx([True, True])
   True


- `13119 &lt;https://github.com/pytest-dev/pytest/issues/13119&gt;`_: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.


- `13175 &lt;https://github.com/pytest-dev/pytest/issues/13175&gt;`_: The diff is now also highlighted correctly when comparing two strings.


- `13248 &lt;https://github.com/pytest-dev/pytest/issues/13248&gt;`_: Fixed an issue where passing a ``scope`` in :py:func:`Metafunc.parametrize &lt;pytest.Metafunc.parametrize&gt;` with ``indirect=True``
could result in other fixtures being unable to depend on the parametrized fixture.


- `13291 &lt;https://github.com/pytest-dev/pytest/issues/13291&gt;`_: Fixed ``repr`` of ``attrs`` objects in assertion failure messages when using ``attrs&gt;=25.2``.


- `13312 &lt;https://github.com/pytest-dev/pytest/issues/13312&gt;`_: Fixed a possible ``KeyError`` crash on PyPy during collection of tests involving higher-scoped parameters.


- `13345 &lt;https://github.com/pytest-dev/pytest/issues/13345&gt;`_: Fix type hints for :attr:`pytest.TestReport.when` and :attr:`pytest.TestReport.location`.


- `13377 &lt;https://github.com/pytest-dev/pytest/issues/13377&gt;`_: 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.:

.. code-block:: python

   class TestClass:

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

Before, this caused an internal error in pytest.


- `13384 &lt;https://github.com/pytest-dev/pytest/issues/13384&gt;`_: Fixed an issue where pytest could report negative durations.


- `13420 &lt;https://github.com/pytest-dev/pytest/issues/13420&gt;`_: Added ``lru_cache`` to ``nodes._check_initialpaths_for_relpath``.


- `9037 &lt;https://github.com/pytest-dev/pytest/issues/9037&gt;`_: Honor :confval:`disable_test_id_escaping_and_forfeit_all_rights_to_community_support` when escaping ids in parametrized tests.



Improved documentation
----------------------

- `12535 &lt;https://github.com/pytest-dev/pytest/issues/12535&gt;`_: `This
example`&lt;https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures&gt;
showed ``print`` statements that do not exactly reflect what the
different branches actually do.  The fix makes the example more precise.


- `13218 &lt;https://github.com/pytest-dev/pytest/issues/13218&gt;`_: Pointed out in the :func:`pytest.approx` documentation that it considers booleans unequal to numeric zero or one.


- `13221 &lt;https://github.com/pytest-dev/pytest/issues/13221&gt;`_: Improved grouping of CLI options in the ``--help`` output.


- `6649 &lt;https://github.com/pytest-dev/pytest/issues/6649&gt;`_: Added :class:`~pytest.TerminalReporter` to the :ref:`api-reference` documentation page.


- `8612 &lt;https://github.com/pytest-dev/pytest/issues/8612&gt;`_: 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 &lt;https://github.com/pytest-dev/pytest/issues/13317&gt;`_: Specified minimum allowed versions of ``colorama``, ``iniconfig``,
and ``packaging``; and bumped the minimum allowed version
of ``exceptiongroup`` for ``python_version&lt;&#x27;3.11&#x27;`` from a release
candidate to a full release.



Contributor-facing changes
--------------------------

- `12017 &lt;https://github.com/pytest-dev/pytest/issues/12017&gt;`_: Mixed internal improvements:

* Migrate formatting to f-strings in some tests.
* Use type-safe constructs in JUnitXML tests.
* Moved`` MockTiming`` into ``_pytest.timing``.

-- by :user:`RonnyPfannschmidt`


- `12647 &lt;https://github.com/pytest-dev/pytest/issues/12647&gt;`_: Fixed running the test suite with the ``hypothesis`` pytest plugin.



Miscellaneous internal changes
------------------------------

- `6649 &lt;https://github.com/pytest-dev/pytest/issues/6649&gt;`_: Added :class:`~pytest.TerminalReporter` to the public pytest API, as it is part of the signature of the :hook:`pytest_terminal_summary` hook.

8.3.5

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

Bug fixes
---------

- `11777 &lt;https://github.com/pytest-dev/pytest/issues/11777&gt;`_: Fixed issue where sequences were still being shortened even with ``-vv`` verbosity.


- `12888 &lt;https://github.com/pytest-dev/pytest/issues/12888&gt;`_: Fixed broken input when using Python 3.13+ and a ``libedit`` build of Python, such as on macOS or with uv-managed Python binaries from the ``python-build-standalone`` project. This could manifest e.g. by a broken prompt when using ``Pdb``, or seeing empty inputs with manual usage of ``input()`` and suspended capturing.


- `13026 &lt;https://github.com/pytest-dev/pytest/issues/13026&gt;`_: Fixed :class:`AttributeError`  crash when using ``--import-mode=importlib`` when top-level directory same name as another module of the standard library.


- `13053 &lt;https://github.com/pytest-dev/pytest/issues/13053&gt;`_: Fixed a regression in pytest 8.3.4 where, when using ``--import-mode=importlib``, a directory containing py file with the same name would cause an ``ImportError``


- `13083 &lt;https://github.com/pytest-dev/pytest/issues/13083&gt;`_: Fixed issue where pytest could crash if one of the collected directories got removed during collection.



Improved documentation
----------------------

- `12842 &lt;https://github.com/pytest-dev/pytest/issues/12842&gt;`_: Added dedicated page about using types with pytest.

See :ref:`types` for detailed usage.



Contributor-facing changes
--------------------------

- `13112 &lt;https://github.com/pytest-dev/pytest/issues/13112&gt;`_: Fixed selftest failures in ``test_terminal.py`` with Pygments &gt;= 2.19.0


- `13256 &lt;https://github.com/pytest-dev/pytest/issues/13256&gt;`_: Support for Towncrier versions released in 2024 has been re-enabled
when building Sphinx docs -- by :user:`webknjaz`.

8.3.4

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

Bug fixes
---------

- `12592 &lt;https://github.com/pytest-dev/pytest/issues/12592&gt;`_: Fixed :class:`KeyError` crash when using ``--import-mode=importlib`` in a directory layout where a directory contains a child directory with the same name.


- `12818 &lt;https://github.com/pytest-dev/pytest/issues/12818&gt;`_: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the ``AST``, like `executing &lt;https://github.com/alexmojaki/executing&gt;`__.


- `12849 &lt;https://github.com/pytest-dev/pytest/issues/12849&gt;`_: ANSI escape codes for colored output now handled correctly in :func:`pytest.fail` with `pytrace=False`.


- `9353 &lt;https://github.com/pytest-dev/pytest/issues/9353&gt;`_: :func:`pytest.approx` now uses strict equality when given booleans.



Improved documentation
----------------------

- `10558 &lt;https://github.com/pytest-dev/pytest/issues/10558&gt;`_: Fix ambiguous docstring of :func:`pytest.Config.getoption`.


- `10829 &lt;https://github.com/pytest-dev/pytest/issues/10829&gt;`_: Improve documentation on the current handling of the ``--basetemp`` option and its lack of retention functionality (:ref:`temporary directory location and retention`).


- `12866 &lt;https://github.com/pytest-dev/pytest/issues/12866&gt;`_: Improved cross-references concerning the :fixture:`recwarn` fixture.


- `12966 &lt;https://github.com/pytest-dev/pytest/issues/12966&gt;`_: Clarify :ref:`filterwarnings` docs on filter precedence/order when using multiple :ref:`pytest.mark.filterwarnings &lt;pytest.mark.filterwarnings ref&gt;` marks.



Contributor-facing changes
--------------------------

- `12497 &lt;https://github.com/pytest-dev/pytest/issues/12497&gt;`_: Fixed two failing pdb-related tests on Python 3.13.

8.3.3

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

Bug fixes
---------

- `12446 &lt;https://github.com/pytest-dev/pytest/issues/12446&gt;`_: Avoid calling ``property`` (and other instance descriptors) during fixture discovery -- by :user:`asottile`


- `12659 &lt;https://github.com/pytest-dev/pytest/issues/12659&gt;`_: Fixed the issue of not displaying assertion failure differences when using the parameter ``--import-mode=importlib`` in pytest&gt;=8.1.


- `12667 &lt;https://github.com/pytest-dev/pytest/issues/12667&gt;`_: Fixed a regression where type change in `ExceptionInfo.errisinstance` caused `mypy` to fail.


- `12744 &lt;https://github.com/pytest-dev/pytest/issues/12744&gt;`_: Fixed typing compatibility with Python 3.9 or less -- replaced `typing.Self` with `typing_extensions.Self` -- by :user:`Avasam`


- `12745 &lt;https://github.com/pytest-dev/pytest/issues/12745&gt;`_: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.


- `6682 &lt;https://github.com/pytest-dev/pytest/issues/6682&gt;`_: Fixed bug where the verbosity levels where not being respected when printing the &quot;msg&quot; part of failed assertion (as in ``assert condition, msg``).


- `9422 &lt;https://github.com/pytest-dev/pytest/issues/9422&gt;`_: Fix bug where disabling the terminal plugin via ``-p no:terminal`` would cause crashes related to missing the ``verbose`` option.

-- by :user:`GTowers1`



Improved documentation
----------------------

- `12663 &lt;https://github.com/pytest-dev/pytest/issues/12663&gt;`_: Clarify that the `pytest_deselected` hook should be called from `pytest_collection_modifyitems` hook implementations when items are deselected.


- `12678 &lt;https://github.com/pytest-dev/pytest/issues/12678&gt;`_: Remove erroneous quotes from `tmp_path_retention_policy` example in docs.



Miscellaneous internal changes
------------------------------

- `12769 &lt;https://github.com/pytest-dev/pytest/issues/12769&gt;`_: Fix typos discovered by codespell and add codespell to pre-commit hooks.

8.3.2

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

Bug fixes
---------

- `12652 &lt;https://github.com/pytest-dev/pytest/issues/12652&gt;`_: Resolve regression `conda` environments where no longer being automatically detected.

-- by :user:`RonnyPfannschmidt`

8.3.1

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

The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.

8.3.0

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

New features
------------

- `12231 &lt;https://github.com/pytest-dev/pytest/issues/12231&gt;`_: Added `--xfail-tb` flag, which turns on traceback output for XFAIL results.

* If the `--xfail-tb` flag is not given, tracebacks for XFAIL results are NOT shown.
* The style of traceback for XFAIL is set with `--tb`, and can be `auto|long|short|line|native|no`.
* Note: Even if you have `--xfail-tb` set, you won&#x27;t see them if `--tb=no`.

Some history:

With pytest 8.0, `-rx` or `-ra` would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don&#x27;t want to see all of the xfail tracebacks.

This change detaches xfail tracebacks from `-rx`, and now we turn on xfail tracebacks with `--xfail-tb`. With this, the default `-rx`/ `-ra` behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.

-- by :user:`okken`


- `12281 &lt;https://github.com/pytest-dev/pytest/issues/12281&gt;`_: Added support for keyword matching in marker expressions.

Now tests can be selected by marker keyword arguments.
Supported values are :class:`int`, (unescaped) :class:`str`, :class:`bool` &amp; :data:`None`.

See :ref:`marker examples &lt;marker_keyword_expression_example&gt;` for more information.

-- by :user:`lovetheguitar`


- `12567 &lt;https://github.com/pytest-dev/pytest/issues/12567&gt;`_: Added ``--no-fold-skipped`` command line option.

If this option is set, then skipped tests in short summary are no longer grouped
by reason but all tests are printed individually with their nodeid in the same
way as other statuses.

-- by :user:`pbrezina`



Improvements in existing functionality
--------------------------------------

- `12469 &lt;https://github.com/pytest-dev/pytest/issues/12469&gt;`_: The console output now uses the &quot;third-party plugins&quot; terminology,
replacing the previously established but confusing and outdated
reference to :std:doc:`setuptools &lt;setuptools:index&gt;`
-- by :user:`webknjaz`.


- `12544 &lt;https://github.com/pytest-dev/pytest/issues/12544&gt;`_, `#12545 &lt;https://github.com/pytest-dev/pytest/issues/12545&gt;`_: Python virtual environment detection was improved by
checking for a :file:`pyvenv.cfg` file, ensuring reliable detection on
various platforms -- by :user:`zachsnickers`.


- `2871 &lt;https://github.com/pytest-dev/pytest/issues/2871&gt;`_: Do not truncate arguments to functions in output when running with `-vvv`.


- `389 &lt;https://github.com/pytest-dev/pytest/issues/389&gt;`_: The readability of assertion introspection of bound methods has been enhanced
-- by :user:`farbodahm`, :user:`webknjaz`, :user:`obestwalter`, :user:`flub`
and :user:`glyphack`.

Earlier, it was like:

.. code-block:: console

   =================================== FAILURES ===================================
   _____________________________________ test _____________________________________

       def test():
   &gt;       assert Help().fun() == 2
   E       assert 1 == 2
   E        +  where 1 = &lt;bound method Help.fun of &lt;example.Help instance at 0x256a830&gt;&gt;()
   E        +    where &lt;bound method Help.fun of &lt;example.Help instance at 0x256a830&gt;&gt; = &lt;example.Help instance at 0x256a830&gt;.fun
   E        +      where &lt;example.Help instance at 0x256a830&gt; = Help()

   example.py:7: AssertionError
   =========================== 1 failed in 0.03 seconds ===========================


And now it&#x27;s like:

.. code-block:: console

   =================================== FAILURES ===================================
   _____________________________________ test _____________________________________

       def test():
   &gt;       assert Help().fun() == 2
   E       assert 1 == 2
   E        +  where 1 = fun()
   E        +    where fun = &lt;test_local.Help object at 0x1074be230&gt;.fun
   E        +      where &lt;test_local.Help object at 0x1074be230&gt; = Help()

   test_local.py:13: AssertionError
   =========================== 1 failed in 0.03 seconds ===========================


- `7662 &lt;https://github.com/pytest-dev/pytest/issues/7662&gt;`_: Added timezone information to the testsuite timestamp in the JUnit XML report.



Bug fixes
---------

- `11706 &lt;https://github.com/pytest-dev/pytest/issues/11706&gt;`_: Fixed reporting of teardown errors in higher-scoped fixtures when using `--maxfail` or `--stepwise`.

Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist.
This regression was fixed in pytest-xdist 3.6.1.


- `11797 &lt;https://github.com/pytest-dev/pytest/issues/11797&gt;`_: :func:`pytest.approx` now correctly handles :class:`Sequence &lt;collections.abc.Sequence&gt;`-like objects.


- `12204 &lt;https://github.com/pytest-dev/pytest/issues/12204&gt;`_, `#12264 &lt;https://github.com/pytest-dev/pytest/issues/12264&gt;`_: Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
tests fail due to a shared higher-scope fixture which raised -- by :user:`bluetech`.

Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.

The fix necessitated internal changes which may affect some plugins:

* ``FixtureDef.cached_result[2]`` is now a tuple ``(exc, tb)``
 instead of ``exc``.
* ``SetupState.stack`` failures are now a tuple ``(exc, tb)``
 instead of ``exc``.


- `12275 &lt;https://github.com/pytest-dev/pytest/issues/12275&gt;`_: Fixed collection error upon encountering an :mod:`abstract &lt;abc&gt;` class, including abstract `unittest.TestCase` subclasses.


- `12328 &lt;https://github.com/pytest-dev/pytest/issues/12328&gt;`_: Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.


- `12424 &lt;https://github.com/pytest-dev/pytest/issues/12424&gt;`_: Fixed crash with `assert testcase is not None` assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2.


- `12472 &lt;https://github.com/pytest-dev/pytest/issues/12472&gt;`_: Fixed a crash when returning category ``&quot;error&quot;`` or ``&quot;failed&quot;`` with a custom test status from :hook:`pytest_report_teststatus` hook -- :user:`pbrezina`.


- `12505 &lt;https://github.com/pytest-dev/pytest/issues/12505&gt;`_: Improved handling of invalid regex patterns in :func:`pytest.raises(match=r&#x27;...&#x27;) &lt;pytest.raises&gt;` by providing a clear error message.


- `12580 &lt;https://github.com/pytest-dev/pytest/issues/12580&gt;`_: Fixed a crash when using the cache class on Windows and the cache directory was created concurrently.


- `6962 &lt;https://github.com/pytest-dev/pytest/issues/6962&gt;`_: Parametrization parameters are now compared using `==` instead of `is` (`is` is still used as a fallback if the parameter does not support `==`).
This fixes use of parameters such as lists, which have a different `id` but compare equal, causing fixtures to be re-computed instead of being cached.


- `7166 &lt;https://github.com/pytest-dev/pytest/issues/7166&gt;`_: Fixed progress percentages (the ``[ 87%]`` at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist ``-n``.



Improved documentation
----------------------

- `12153 &lt;https://github.com/pytest-dev/pytest/issues/12153&gt;`_: Documented using :envvar:`PYTEST_VERSION` to detect if code is running from within a pytest run.


- `12469 &lt;https://github.com/pytest-dev/pytest/issues/12469&gt;`_: The external plugin mentions in the documentation now avoid mentioning
:std:doc:`setuptools entry-points &lt;setuptools:index&gt;` as the concept is
much more generic nowadays. Instead, the terminology of &quot;external&quot;,
&quot;installed&quot;, or &quot;third-party&quot; plugins (or packages) replaces that.

-- by :user:`webknjaz`


- `12577 &lt;https://github.com/pytest-dev/pytest/issues/12577&gt;`_: `CI` and `BUILD_NUMBER` environment variables role is described in
the reference doc. They now also appear when doing `pytest -h`
-- by :user:`MarcBresson`.



Contributor-facing changes
--------------------------

- `12467 &lt;https://github.com/pytest-dev/pytest/issues/12467&gt;`_: Migrated all internal type-annotations to the python3.10+ style by using the `annotations` future import.

-- by :user:`RonnyPfannschmidt`


- `11771 &lt;https://github.com/pytest-dev/pytest/issues/11771&gt;`_, `#12557 &lt;https://github.com/pytest-dev/pytest/issues/12557&gt;`_: The PyPy runtime version has been updated to 3.9 from 3.8 that introduced
a flaky bug at the garbage collector which was not expected to fix there
as the 3.8 is EoL.

-- by :user:`x612skm`


- `12493 &lt;https://github.com/pytest-dev/pytest/issues/12493&gt;`_: The change log draft preview integration has been refactored to use a
third party extension ``sphinxcontib-towncrier``. The previous in-repo
script was putting the change log preview file at
:file:`doc/en/_changelog_towncrier_draft.rst`. Said file is no longer
ignored in Git and might show up among untracked files in the
development environments of the contributors. To address that, the
contributors can run the following command that will clean it up:

.. code-block:: console

  $ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst

-- by :user:`webknjaz`


- `12498 &lt;https://github.com/pytest-dev/pytest/issues/12498&gt;`_: All the undocumented ``tox`` environments now have descriptions.
They can be listed in one&#x27;s development environment by invoking
``tox -av`` in a terminal.

-- by :user:`webknjaz`


- `12501 &lt;https://github.com/pytest-dev/pytest/issues/12501&gt;`_: The changelog configuration has been updated to introduce more accurate
audience-tailored categories. Previously, there was a ``trivial``
change log fragment type with an unclear and broad meaning. It was
removed and we now have ``contrib``, ``misc`` and ``packaging`` in
place of it.

The new change note types target the readers who are downstream
packagers and project contributors. Additionally, the miscellaneous
section is kept for unspecified updates that do not fit anywhere else.

-- by :user:`webknjaz`


- `12502 &lt;https://github.com/pytest-dev/pytest/issues/12502&gt;`_: The UX of the GitHub automation making pull requests to update the
plugin list has been updated. Previously, the maintainers had to close
the 

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **Chores**
* Updated development dependency versions to ensure testing environment consistency and stability.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

coderabbitai · 2026-04-08T13:05:02Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: eccbfc27-7209-48fa-8573-41f827775f94

📥 Commits

Reviewing files that changed from the base of the PR and between d377ad0 and 62d5f04.

📒 Files selected for processing (1)

src/requirements_dev.txt

📝 Walkthrough

Walkthrough

The development requirements file now pins pytest to version 9.0.3 instead of an unversioned dependency. This is a single-line configuration change with no impact on public APIs or exported entities.

Changes

Cohort / File(s)	Summary
Dependency Version Pinning `src/requirements_dev.txt`	Pinned `pytest` to specific version `9.0.3` for development environment consistency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version pinned, so neat and tight,
Pytest now locked in place just right,
No more surprises in the night,
Development's future shining bright! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: pinning pytest to version 9.0.3 in the development requirements file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch pyup-pin-pytest-9.0.3

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Pin pytest to latest version 9.0.3

62d5f04

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pin pytest to latest version 9.0.3 - #563

Pin pytest to latest version 9.0.3#563
pyup-bot wants to merge 1 commit into
masterfrom
pyup-pin-pytest-9.0.3

pyup-bot commented Apr 8, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Apr 8, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

pyup-bot commented Apr 8, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

9.0.3

9.0.2

9.0.1

9.0.0

8.4.2

8.4.1

8.4.0

8.3.5

8.3.4

8.3.3

8.3.2

8.3.1

8.3.0

Uh oh!

coderabbitai Bot commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

pyup-bot commented Apr 8, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Apr 8, 2026 •

edited

Loading