Update pytest to 8.0.0 #325

pyup-bot · 2024-01-28T17:13:10Z

This PR updates pytest from 3.8.2 to 8.0.0.

Changelog

8.0.0

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

Bug Fixes
---------

- `11842 &lt;https://github.com/pytest-dev/pytest/issues/11842&gt;`_: Properly escape the ``reason`` of a :ref:`skip &lt;pytest.mark.skip ref&gt;` mark when writing JUnit XML files.


- `11861 &lt;https://github.com/pytest-dev/pytest/issues/11861&gt;`_: Avoid microsecond exceeds ``1_000_000`` when using ``log-date-format`` with ``%f`` specifier, which might cause the test suite to crash.

8.0.0rc2

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


Improvements
------------

- `11233 &lt;https://github.com/pytest-dev/pytest/issues/11233&gt;`_: Improvements to ``-r`` for xfailures and xpasses:

* Report tracebacks for xfailures when ``-rx`` is set.
* Report captured output for xpasses when ``-rX`` is set.
* For xpasses, add ``-`` in summary between test name and reason, to match how xfail is displayed.

- `11825 &lt;https://github.com/pytest-dev/pytest/issues/11825&gt;`_: The :hook:`pytest_plugin_registered` hook has a new ``plugin_name`` parameter containing the name by which ``plugin`` is registered.


Bug Fixes
---------

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


- `11758 &lt;https://github.com/pytest-dev/pytest/issues/11758&gt;`_: Fixed ``IndexError: string index out of range`` crash in ``if highlighted[-1] == &quot;\n&quot; and source[-1] != &quot;\n&quot;``.
This bug was introduced in pytest 8.0.0rc1.


- `9765 &lt;https://github.com/pytest-dev/pytest/issues/9765&gt;`_, `#11816 &lt;https://github.com/pytest-dev/pytest/issues/11816&gt;`_: Fixed a frustrating bug that afflicted some users with the only error being ``assert mod not in mods``. The issue was caused by the fact that ``str(Path(mod))`` and ``mod.__file__`` don&#x27;t necessarily produce the same string, and was being erroneously used interchangably in some places in the code.

This fix also broke the internal API of ``PytestPluginManager.consider_conftest`` by introducing a new parameter -- we mention this in case it is being used by external code, even if marked as *private*.

8.0.0rc1

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

Breaking Changes
----------------

Old Deprecations Are Now Errors
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

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

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

In the pytest ``8.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.PytestRemovedIn8Warning

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

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


Version Compatibility
^^^^^^^^^^^^^^^^^^^^^

- `11151 &lt;https://github.com/pytest-dev/pytest/issues/11151&gt;`_: Dropped support for Python 3.7, which `reached end-of-life on 2023-06-27 &lt;https://devguide.python.org/versions/&gt;`__.


- ``pluggy&gt;=1.3.0`` is now required.


Collection Changes
^^^^^^^^^^^^^^^^^^

In this version we&#x27;ve made several breaking changes to pytest&#x27;s collection phase,
particularly around how filesystem directories and Python packages are collected,
fixing deficiencies and allowing for cleanups and improvements to pytest&#x27;s internals.
A deprecation period for these changes was not possible.


- `7777 &lt;https://github.com/pytest-dev/pytest/issues/7777&gt;`_: Files and directories are now collected in alphabetical order jointly, unless changed by a plugin.
Previously, files were collected before directories.
See below for an example.


- `8976 &lt;https://github.com/pytest-dev/pytest/issues/8976&gt;`_: Running `pytest pkg/__init__.py` now collects the `pkg/__init__.py` file (module) only.
Previously, it collected the entire `pkg` package, including other test files in the directory, but excluding tests in the `__init__.py` file itself
(unless :confval:`python_files` was changed to allow `__init__.py` file).

To collect the entire package, specify just the directory: `pytest pkg`.


- `11137 &lt;https://github.com/pytest-dev/pytest/issues/11137&gt;`_: :class:`pytest.Package` is no longer a :class:`pytest.Module` or :class:`pytest.File`.

The ``Package`` collector node designates a Python package, that is, a directory with an `__init__.py` file.
Previously ``Package`` was a subtype of ``pytest.Module`` (which represents a single Python module),
the module being the `__init__.py` file.
This has been deemed a design mistake (see :issue:`11137` and :issue:`7777` for details).

The ``path`` property of ``Package`` nodes now points to the package directory instead of the ``__init__.py`` file.

Note that a ``Module`` node for ``__init__.py`` (which is not a ``Package``) may still exist,
if it is picked up during collection (e.g. if you configured :confval:`python_files` to include ``__init__.py`` files).


- `7777 &lt;https://github.com/pytest-dev/pytest/issues/7777&gt;`_: Added a new :class:`pytest.Directory` base collection node, which all collector nodes for filesystem directories are expected to subclass.
This is analogous to the existing :class:`pytest.File` for file nodes.

Changed :class:`pytest.Package` to be a subclass of :class:`pytest.Directory`.
A ``Package`` represents a filesystem directory which is a Python package,
i.e. contains an ``__init__.py`` file.

:class:`pytest.Package` now only collects files in its own directory; previously it collected recursively.
Sub-directories are collected as their own collector nodes, which then collect themselves, thus creating a collection tree which mirrors the filesystem hierarchy.

Added a new :class:`pytest.Dir` concrete collection node, a subclass of :class:`pytest.Directory`.
This node represents a filesystem directory, which is not a :class:`pytest.Package`,
that is, does not contain an ``__init__.py`` file.
Similarly to ``Package``, it only collects the files in its own directory.

:class:`pytest.Session` now only collects the initial arguments, without recursing into directories.
This work is now done by the :func:`recursive expansion process &lt;pytest.Collector.collect&gt;` of directory collector nodes.

:attr:`session.name &lt;pytest.Session.name&gt;` is now ``&quot;&quot;``; previously it was the rootdir directory name.
This matches :attr:`session.nodeid &lt;_pytest.nodes.Node.nodeid&gt;` which has always been `&quot;&quot;`.

The collection tree now contains directories/packages up to the :ref:`rootdir &lt;rootdir&gt;`,
for initial arguments that are found within the rootdir.
For files outside the rootdir, only the immediate directory/package is collected --
note however that collecting from outside the rootdir is discouraged.

As an example, given the following filesystem tree::

   myroot/
       pytest.ini
       top/
       ├── aaa
       │   └── test_aaa.py
       ├── test_a.py
       ├── test_b
       │   ├── __init__.py
       │   └── test_b.py
       ├── test_c.py
       └── zzz
           ├── __init__.py
           └── test_zzz.py

the collection tree, as shown by `pytest --collect-only top/` but with the otherwise-hidden :class:`~pytest.Session` node added for clarity,
is now the following::

   &lt;Session&gt;
     &lt;Dir myroot&gt;
       &lt;Dir top&gt;
         &lt;Dir aaa&gt;
           &lt;Module test_aaa.py&gt;
             &lt;Function test_it&gt;
         &lt;Module test_a.py&gt;
           &lt;Function test_it&gt;
         &lt;Package test_b&gt;
           &lt;Module test_b.py&gt;
             &lt;Function test_it&gt;
         &lt;Module test_c.py&gt;
           &lt;Function test_it&gt;
         &lt;Package zzz&gt;
           &lt;Module test_zzz.py&gt;
             &lt;Function test_it&gt;

Previously, it was::

   &lt;Session&gt;
     &lt;Module top/test_a.py&gt;
       &lt;Function test_it&gt;
     &lt;Module top/test_c.py&gt;
       &lt;Function test_it&gt;
     &lt;Module top/aaa/test_aaa.py&gt;
       &lt;Function test_it&gt;
     &lt;Package test_b&gt;
       &lt;Module test_b.py&gt;
         &lt;Function test_it&gt;
     &lt;Package zzz&gt;
       &lt;Module test_zzz.py&gt;
         &lt;Function test_it&gt;

Code/plugins which rely on a specific shape of the collection tree might need to update.


- `11676 &lt;https://github.com/pytest-dev/pytest/issues/11676&gt;`_: The classes :class:`~_pytest.nodes.Node`, :class:`~pytest.Collector`, :class:`~pytest.Item`, :class:`~pytest.File`, :class:`~_pytest.nodes.FSCollector` are now marked abstract (see :mod:`abc`).

We do not expect this change to affect users and plugin authors, it will only cause errors when the code is already wrong or problematic.


Other breaking changes
^^^^^^^^^^^^^^^^^^^^^^

These are breaking changes where deprecation was not possible.


- `11282 &lt;https://github.com/pytest-dev/pytest/issues/11282&gt;`_: Sanitized the handling of the ``default`` parameter when defining configuration options.

Previously if ``default`` was not supplied for :meth:`parser.addini &lt;pytest.Parser.addini&gt;` and the configuration option value was not defined in a test session, then calls to :func:`config.getini &lt;pytest.Config.getini&gt;` returned an *empty list* or an *empty string* depending on whether ``type`` was supplied or not respectively, which is clearly incorrect. Also, ``None`` was not honored even if ``default=None`` was used explicitly while defining the option.

Now the behavior of :meth:`parser.addini &lt;pytest.Parser.addini&gt;` is as follows:

* If ``default`` is NOT passed but ``type`` is provided, then a type-specific default will be returned. For example ``type=bool`` will return ``False``, ``type=str`` will return ``&quot;&quot;``, etc.
* If ``default=None`` is passed and the option is not defined in a test session, then ``None`` will be returned, regardless of the ``type``.
* If neither ``default`` nor ``type`` are provided, assume ``type=str`` and return ``&quot;&quot;`` as default (this is as per previous behavior).

The team decided to not introduce a deprecation period for this change, as doing so would be complicated both in terms of communicating this to the community as well as implementing it, and also because the team believes this change should not break existing plugins except in rare cases.


- `11667 &lt;https://github.com/pytest-dev/pytest/issues/11667&gt;`_: pytest&#x27;s ``setup.py`` file is removed.
If you relied on this file, e.g. to install pytest using ``setup.py install``,
please see `Why you shouldn&#x27;t invoke setup.py directly &lt;https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary&gt;`_ for alternatives.


- `9288 &lt;https://github.com/pytest-dev/pytest/issues/9288&gt;`_: :func:`~pytest.warns` now re-emits unmatched warnings when the context
closes -- previously it would consume all warnings, hiding those that were not
matched by the function.

While this is a new feature, we announce it as a breaking change
because many test suites are configured to error-out on warnings, and will
therefore fail on the newly-re-emitted warnings.



Deprecations
------------

- `10465 &lt;https://github.com/pytest-dev/pytest/issues/10465&gt;`_: Test functions returning a value other than ``None`` will now issue a :class:`pytest.PytestWarning` instead of ``pytest.PytestRemovedIn8Warning``, meaning this will stay a warning instead of becoming an error in the future.


- `3664 &lt;https://github.com/pytest-dev/pytest/issues/3664&gt;`_: Applying a mark to a fixture function now issues a warning: marks in fixtures never had any effect, but it is a common user error to apply a mark to a fixture (for example ``usefixtures``) and expect it to work.

This will become an error in pytest 9.0.



Features and Improvements
-------------------------

Improved Diffs
^^^^^^^^^^^^^^

These changes improve the diffs that pytest prints when an assertion fails.
Note that syntax highlighting requires the ``pygments`` package.


- `11520 &lt;https://github.com/pytest-dev/pytest/issues/11520&gt;`_: The very verbose (``-vv``) diff output is now colored as a diff instead of a big chunk of red.

Python code in error reports is now syntax-highlighted as Python.

The sections in the error reports are now better separated.


- `1531 &lt;https://github.com/pytest-dev/pytest/issues/1531&gt;`_: The very verbose diff (``-vv``) for every standard library container type is improved. The indentation is now consistent and the markers are on their own separate lines, which should reduce the diffs shown to users.

Previously, the standard Python pretty printer was used to generate the output, which puts opening and closing
markers on the same line as the first/last entry, in addition to not having consistent indentation.


- `10617 &lt;https://github.com/pytest-dev/pytest/issues/10617&gt;`_: Added more comprehensive set assertion rewrites for comparisons other than equality ``==``, with
the following operations now providing better failure messages: ``!=``, ``&lt;=``, ``&gt;=``, ``&lt;``, and ``&gt;``.


Separate Control For Assertion Verbosity
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- `11387 &lt;https://github.com/pytest-dev/pytest/issues/11387&gt;`_: Added the new :confval:`verbosity_assertions` configuration option for fine-grained control of failed assertions verbosity.

If you&#x27;ve ever wished that pytest always show you full diffs, but without making everything else verbose, this is for you.

See :ref:`Fine-grained verbosity &lt;pytest.fine_grained_verbosity&gt;` for more details.

For plugin authors, :attr:`config.get_verbosity &lt;pytest.Config.get_verbosity&gt;` can be used to retrieve the verbosity level for a specific verbosity type.


Additional Support For Exception Groups and ``__notes__``
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

These changes improve pytest&#x27;s support for exception groups.


- `10441 &lt;https://github.com/pytest-dev/pytest/issues/10441&gt;`_: Added :func:`ExceptionInfo.group_contains() &lt;pytest.ExceptionInfo.group_contains&gt;`, an assertion helper that tests if an :class:`ExceptionGroup` contains a matching exception.

See :ref:`assert-matching-exception-groups` for an example.


- `11227 &lt;https://github.com/pytest-dev/pytest/issues/11227&gt;`_: Allow :func:`pytest.raises` ``match`` argument to match against `PEP-678 &lt;https://peps.python.org/pep-0678/&gt;` ``__notes__``.


Custom Directory collectors
^^^^^^^^^^^^^^^^^^^^^^^^^^^

- `7777 &lt;https://github.com/pytest-dev/pytest/issues/7777&gt;`_: Added a new hook :hook:`pytest_collect_directory`,
which is called by filesystem-traversing collector nodes,
such as :class:`pytest.Session`, :class:`pytest.Dir` and :class:`pytest.Package`,
to create a collector node for a sub-directory.
It is expected to return a subclass of :class:`pytest.Directory`.
This hook allows plugins to :ref:`customize the collection of directories &lt;custom directory collectors&gt;`.


&quot;New-style&quot; Hook Wrappers
^^^^^^^^^^^^^^^^^^^^^^^^^

- `11122 &lt;https://github.com/pytest-dev/pytest/issues/11122&gt;`_: pytest now uses &quot;new-style&quot; hook wrappers internally, available since pluggy 1.2.0.
See `pluggy&#x27;s 1.2.0 changelog &lt;https://pluggy.readthedocs.io/en/latest/changelog.html#pluggy-1-2-0-2023-06-21&gt;`_ and the :ref:`updated docs &lt;hookwrapper&gt;` for details.

Plugins which want to use new-style wrappers can do so if they require ``pytest&gt;=8``.


Other Improvements
^^^^^^^^^^^^^^^^^^

- `11216 &lt;https://github.com/pytest-dev/pytest/issues/11216&gt;`_: If a test is skipped from inside an :ref:`xunit setup fixture &lt;classic xunit&gt;`, the test summary now shows the test location instead of the fixture location.


- `11314 &lt;https://github.com/pytest-dev/pytest/issues/11314&gt;`_: Logging to a file using the ``--log-file`` option will use ``--log-level``, ``--log-format`` and ``--log-date-format`` as fallback
if ``--log-file-level``, ``--log-file-format`` and ``--log-file-date-format`` are not provided respectively.


- `11610 &lt;https://github.com/pytest-dev/pytest/issues/11610&gt;`_: Added the :func:`LogCaptureFixture.filtering() &lt;pytest.LogCaptureFixture.filtering&gt;` context manager which
adds a given :class:`logging.Filter` object to the :fixture:`caplog` fixture.


- `11447 &lt;https://github.com/pytest-dev/pytest/issues/11447&gt;`_: :func:`pytest.deprecated_call` now also considers warnings of type :class:`FutureWarning`.


- `11600 &lt;https://github.com/pytest-dev/pytest/issues/11600&gt;`_: Improved the documentation and type signature for :func:`pytest.mark.xfail &lt;pytest.mark.xfail&gt;`&#x27;s ``condition`` param to use ``False`` as the default value.


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: :class:`~pytest.FixtureDef` is now exported as ``pytest.FixtureDef`` for typing purposes.


- `11353 &lt;https://github.com/pytest-dev/pytest/issues/11353&gt;`_: Added typing to :class:`~pytest.PytestPluginManager`.


Bug Fixes
---------

- `10701 &lt;https://github.com/pytest-dev/pytest/issues/10701&gt;`_: :meth:`pytest.WarningsRecorder.pop` will return the most-closely-matched warning in the list,
rather than the first warning which is an instance of the requested type.


- `11255 &lt;https://github.com/pytest-dev/pytest/issues/11255&gt;`_: Fixed crash on `parametrize(..., scope=&quot;package&quot;)` without a package present.


- `11277 &lt;https://github.com/pytest-dev/pytest/issues/11277&gt;`_: Fixed a bug that when there are multiple fixtures for an indirect parameter,
the scope of the highest-scope fixture is picked for the parameter set, instead of that of the one with the narrowest scope.


- `11456 &lt;https://github.com/pytest-dev/pytest/issues/11456&gt;`_: Parametrized tests now *really do* ensure that the ids given to each input are unique - for
example, ``a, a, a0`` now results in ``a1, a2, a0`` instead of the previous (buggy) ``a0, a1, a0``.
This necessarily means changing nodeids where these were previously colliding, and for
readability adds an underscore when non-unique ids end in a number.


- `11563 &lt;https://github.com/pytest-dev/pytest/issues/11563&gt;`_: Fixed a crash when using an empty string for the same parametrized value more than once.


- `11712 &lt;https://github.com/pytest-dev/pytest/issues/11712&gt;`_: Fixed handling ``NO_COLOR`` and ``FORCE_COLOR`` to ignore an empty value.


- `9036 &lt;https://github.com/pytest-dev/pytest/issues/9036&gt;`_: ``pytest.warns`` and similar functions now capture warnings when an exception is raised inside a ``with`` block.



Improved Documentation
----------------------

- `11011 &lt;https://github.com/pytest-dev/pytest/issues/11011&gt;`_: Added a warning about modifying the root logger during tests when using ``caplog``.


- `11065 &lt;https://github.com/pytest-dev/pytest/issues/11065&gt;`_: Use ``pytestconfig`` instead of ``request.config`` in cache example to be consistent with the API documentation.


Trivial/Internal Changes
------------------------

- `11208 &lt;https://github.com/pytest-dev/pytest/issues/11208&gt;`_: The (internal) ``FixtureDef.cached_result`` type has changed.
Now the third item ``cached_result[2]``, when set, is an exception instance instead of an exception triplet.


- `11218 &lt;https://github.com/pytest-dev/pytest/issues/11218&gt;`_: (This entry is meant to assist plugins which access private pytest internals to instantiate ``FixtureRequest`` objects.)

:class:`~pytest.FixtureRequest` is now an abstract class which can&#x27;t be instantiated directly.
A new concrete ``TopRequest`` subclass of ``FixtureRequest`` has been added for the ``request`` fixture in test functions,
as counterpart to the existing ``SubRequest`` subclass for the ``request`` fixture in fixture functions.


- `11315 &lt;https://github.com/pytest-dev/pytest/issues/11315&gt;`_: The :fixture:`pytester` fixture now uses the :fixture:`monkeypatch` fixture to manage the current working directory.
If you use ``pytester`` in combination with :func:`monkeypatch.undo() &lt;pytest.MonkeyPatch.undo&gt;`, the CWD might get restored.
Use :func:`monkeypatch.context() &lt;pytest.MonkeyPatch.context&gt;` instead.


- `11333 &lt;https://github.com/pytest-dev/pytest/issues/11333&gt;`_: Corrected the spelling of ``Config.ArgsSource.INVOCATION_DIR``.
The previous spelling ``INCOVATION_DIR`` remains as an alias.


- `11638 &lt;https://github.com/pytest-dev/pytest/issues/11638&gt;`_: Fixed the selftests to pass correctly if ``FORCE_COLOR``, ``NO_COLOR`` or ``PY_COLORS`` is set in the calling environment.

7.4.4

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

Bug Fixes
---------

- `11140 &lt;https://github.com/pytest-dev/pytest/issues/11140&gt;`_: Fix non-string constants at the top of file being detected as docstrings on Python&gt;=3.8.


- `11572 &lt;https://github.com/pytest-dev/pytest/issues/11572&gt;`_: Handle an edge case where :data:`sys.stderr` and :data:`sys.__stderr__` might already be closed when :ref:`faulthandler` is tearing down.


- `11710 &lt;https://github.com/pytest-dev/pytest/issues/11710&gt;`_: Fixed tracebacks from collection errors not getting pruned.


- `7966 &lt;https://github.com/pytest-dev/pytest/issues/7966&gt;`_: Removed unhelpful error message from assertion rewrite mechanism when exceptions are raised in ``__iter__`` methods. Now they are treated un-iterable instead.



Improved Documentation
----------------------

- `11091 &lt;https://github.com/pytest-dev/pytest/issues/11091&gt;`_: Updated documentation to refer to hyphenated options: replaced ``--junitxml`` with ``--junit-xml`` and ``--collectonly`` with ``--collect-only``.

7.4.3

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

Bug Fixes
---------

- `10447 &lt;https://github.com/pytest-dev/pytest/issues/10447&gt;`_: Markers are now considered in the reverse mro order to ensure base  class markers are considered first -- this resolves a regression.


- `11239 &lt;https://github.com/pytest-dev/pytest/issues/11239&gt;`_: Fixed ``:=`` in asserts impacting unrelated test cases.


- `11439 &lt;https://github.com/pytest-dev/pytest/issues/11439&gt;`_: Handled an edge case where :data:`sys.stderr` might already be closed when :ref:`faulthandler` is tearing down.

7.4.2

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

Bug Fixes
---------

- `11237 &lt;https://github.com/pytest-dev/pytest/issues/11237&gt;`_: Fix doctest collection of `functools.cached_property` objects.


- `11306 &lt;https://github.com/pytest-dev/pytest/issues/11306&gt;`_: Fixed bug using ``--importmode=importlib`` which would cause package ``__init__.py`` files to be imported more than once in some cases.


- `11367 &lt;https://github.com/pytest-dev/pytest/issues/11367&gt;`_: Fixed bug where `user_properties` where not being saved in the JUnit XML file if a fixture failed during teardown.


- `11394 &lt;https://github.com/pytest-dev/pytest/issues/11394&gt;`_: Fixed crash when parsing long command line arguments that might be interpreted as files.



Improved Documentation
----------------------

- `11391 &lt;https://github.com/pytest-dev/pytest/issues/11391&gt;`_: Improved disclaimer on pytest plugin reference page to better indicate this is an automated, non-curated listing.

7.4.1

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

Bug Fixes
---------

- `10337 &lt;https://github.com/pytest-dev/pytest/issues/10337&gt;`_: Fixed bug where fake intermediate modules generated by ``--import-mode=importlib`` would not include the
child modules as attributes of the parent modules.


- `10702 &lt;https://github.com/pytest-dev/pytest/issues/10702&gt;`_: Fixed error assertion handling in :func:`pytest.approx` when ``None`` is an expected or received value when comparing dictionaries.


- `10811 &lt;https://github.com/pytest-dev/pytest/issues/10811&gt;`_: Fixed issue when using ``--import-mode=importlib`` together with ``--doctest-modules`` that caused modules
to be imported more than once, causing problems with modules that have import side effects.

7.4.0

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

Features
--------

- `10901 &lt;https://github.com/pytest-dev/pytest/issues/10901&gt;`_: Added :func:`ExceptionInfo.from_exception() &lt;pytest.ExceptionInfo.from_exception&gt;`, a simpler way to create an :class:`~pytest.ExceptionInfo` from an exception.
This can replace :func:`ExceptionInfo.from_exc_info() &lt;pytest.ExceptionInfo.from_exc_info()&gt;` for most uses.



Improvements
------------

- `10872 &lt;https://github.com/pytest-dev/pytest/issues/10872&gt;`_: Update test log report annotation to named tuple and fixed inconsistency in docs for :hook:`pytest_report_teststatus` hook.


- `10907 &lt;https://github.com/pytest-dev/pytest/issues/10907&gt;`_: When an exception traceback to be displayed is completely filtered out (by mechanisms such as ``__tracebackhide__``, internal frames, and similar), now only the exception string and the following message are shown:

&quot;All traceback entries are hidden. Pass `--full-trace` to see hidden and internal frames.&quot;.

Previously, the last frame of the traceback was shown, even though it was hidden.


- `10940 &lt;https://github.com/pytest-dev/pytest/issues/10940&gt;`_: Improved verbose output (``-vv``) of ``skip`` and ``xfail`` reasons by performing text wrapping while leaving a clear margin for progress output.

Added ``TerminalReporter.wrap_write()`` as a helper for that.


- `10991 &lt;https://github.com/pytest-dev/pytest/issues/10991&gt;`_: Added handling of ``%f`` directive to print microseconds in log format options, such as ``log-date-format``.


- `11005 &lt;https://github.com/pytest-dev/pytest/issues/11005&gt;`_: Added the underlying exception to the cache provider&#x27;s path creation and write warning messages.


- `11013 &lt;https://github.com/pytest-dev/pytest/issues/11013&gt;`_: Added warning when :confval:`testpaths` is set, but paths are not found by glob. In this case, pytest will fall back to searching from the current directory.


- `11043 &lt;https://github.com/pytest-dev/pytest/issues/11043&gt;`_: When `--confcutdir` is not specified, and there is no config file present, the conftest cutoff directory (`--confcutdir`) is now set to the :ref:`rootdir &lt;rootdir&gt;`.
Previously in such cases, `conftest.py` files would be probed all the way to the root directory of the filesystem.
If you are badly affected by this change, consider adding an empty config file to your desired cutoff directory, or explicitly set `--confcutdir`.


- `11081 &lt;https://github.com/pytest-dev/pytest/issues/11081&gt;`_: The :confval:`norecursedirs` check is now performed in a :hook:`pytest_ignore_collect` implementation, so plugins can affect it.

If after updating to this version you see that your `norecursedirs` setting is not being respected,
it means that a conftest or a plugin you use has a bad `pytest_ignore_collect` implementation.
Most likely, your hook returns `False` for paths it does not want to ignore,
which ends the processing and doesn&#x27;t allow other plugins, including pytest itself, to ignore the path.
The fix is to return `None` instead of `False` for paths your hook doesn&#x27;t want to ignore.


- `8711 &lt;https://github.com/pytest-dev/pytest/issues/8711&gt;`_: :func:`caplog.set_level() &lt;pytest.LogCaptureFixture.set_level&gt;` and :func:`caplog.at_level() &lt;pytest.LogCaptureFixture.at_level&gt;`
will temporarily enable the requested ``level`` if ``level`` was disabled globally via
``logging.disable(LEVEL)``.



Bug Fixes
---------

- `10831 &lt;https://github.com/pytest-dev/pytest/issues/10831&gt;`_: Terminal Reporting: Fixed bug when running in ``--tb=line`` mode where ``pytest.fail(pytrace=False)`` tests report ``None``.


- `11068 &lt;https://github.com/pytest-dev/pytest/issues/11068&gt;`_: Fixed the ``--last-failed`` whole-file skipping functionality (&quot;skipped N files&quot;) for :ref:`non-python test files &lt;non-python tests&gt;`.


- `11104 &lt;https://github.com/pytest-dev/pytest/issues/11104&gt;`_: Fixed a regression in pytest 7.3.2 which caused to :confval:`testpaths` to be considered for loading initial conftests,
even when it was not utilized (e.g. when explicit paths were given on the command line).
Now the ``testpaths`` are only considered when they are in use.


- `1904 &lt;https://github.com/pytest-dev/pytest/issues/1904&gt;`_: Fixed traceback entries hidden with ``__tracebackhide__ = True`` still being shown for chained exceptions (parts after &quot;... the above exception ...&quot; message).


- `7781 &lt;https://github.com/pytest-dev/pytest/issues/7781&gt;`_: Fix writing non-encodable text to log file when using ``--debug``.



Improved Documentation
----------------------

- `9146 &lt;https://github.com/pytest-dev/pytest/issues/9146&gt;`_: Improved documentation for :func:`caplog.set_level() &lt;pytest.LogCaptureFixture.set_level&gt;`.



Trivial/Internal Changes
------------------------

- `11031 &lt;https://github.com/pytest-dev/pytest/issues/11031&gt;`_: Enhanced the CLI flag for ``-c`` to now include ``--config-file`` to make it clear that this flag applies to the usage of a custom config file.

7.3.2

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

Bug Fixes
---------

- `10169 &lt;https://github.com/pytest-dev/pytest/issues/10169&gt;`_: Fix bug where very long option names could cause pytest to break with ``OSError: [Errno 36] File name too long`` on some systems.


- `10894 &lt;https://github.com/pytest-dev/pytest/issues/10894&gt;`_: Support for Python 3.12 (beta at the time of writing).


- `10987 &lt;https://github.com/pytest-dev/pytest/issues/10987&gt;`_: :confval:`testpaths` is now honored to load root ``conftests``.


- `10999 &lt;https://github.com/pytest-dev/pytest/issues/10999&gt;`_: The `monkeypatch` `setitem`/`delitem` type annotations now allow `TypedDict` arguments.


- `11028 &lt;https://github.com/pytest-dev/pytest/issues/11028&gt;`_: Fixed bug in assertion rewriting where a variable assigned with the walrus operator could not be used later in a function call.


- `11054 &lt;https://github.com/pytest-dev/pytest/issues/11054&gt;`_: Fixed ``--last-failed``&#x27;s &quot;(skipped N files)&quot; functionality for files inside of packages (directories with `__init__.py` files).

7.3.1

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

Improvements
------------

- `10875 &lt;https://github.com/pytest-dev/pytest/issues/10875&gt;`_: Python 3.12 support: fixed ``RuntimeError: TestResult has no addDuration method`` when running ``unittest`` tests.


- `10890 &lt;https://github.com/pytest-dev/pytest/issues/10890&gt;`_: Python 3.12 support: fixed ``shutil.rmtree(onerror=...)`` deprecation warning when using :fixture:`tmp_path`.



Bug Fixes
---------

- `10896 &lt;https://github.com/pytest-dev/pytest/issues/10896&gt;`_: Fixed performance regression related to :fixture:`tmp_path` and the new :confval:`tmp_path_retention_policy` option.


- `10903 &lt;https://github.com/pytest-dev/pytest/issues/10903&gt;`_: Fix crash ``INTERNALERROR IndexError: list index out of range`` which happens when displaying an exception where all entries are hidden.
This reverts the change &quot;Correctly handle ``__tracebackhide__`` for chained exceptions.&quot; introduced in version 7.3.0.

7.3.0

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

Features
--------

- `10525 &lt;https://github.com/pytest-dev/pytest/issues/10525&gt;`_: Test methods decorated with ``classmethod`` can now be discovered as tests, following the same rules as normal methods. This fills the gap that static methods were discoverable as tests but not class methods.


- `10755 &lt;https://github.com/pytest-dev/pytest/issues/10755&gt;`_: :confval:`console_output_style` now supports ``progress-even-when-capture-no`` to force the use of the progress output even when capture is disabled. This is useful in large test suites where capture may have significant performance impact.


- `7431 &lt;https://github.com/pytest-dev/pytest/issues/7431&gt;`_: ``--log-disable`` CLI option added to disable individual loggers.


- `8141 &lt;https://github.com/pytest-dev/pytest/issues/8141&gt;`_: Added :confval:`tmp_path_retention_count` and :confval:`tmp_path_retention_policy` configuration options to control how directories created by the :fixture:`tmp_path` fixture are kept.



Improvements
------------

- `10226 &lt;https://github.com/pytest-dev/pytest/issues/10226&gt;`_: If multiple errors are raised in teardown, we now re-raise an ``ExceptionGroup`` of them instead of discarding all but the last.


- `10658 &lt;https://github.com/pytest-dev/pytest/issues/10658&gt;`_: Allow ``-p`` arguments to include spaces (eg: ``-p no:logging`` instead of
``-pno:logging``). Mostly useful in the ``addopts`` section of the configuration
file.


- `10710 &lt;https://github.com/pytest-dev/pytest/issues/10710&gt;`_: Added ``start`` and ``stop`` timestamps to ``TestReport`` objects.


- `10727 &lt;https://github.com/pytest-dev/pytest/issues/10727&gt;`_: Split the report header for ``rootdir``, ``config file`` and ``testpaths`` so each has its own line.


- `10840 &lt;https://github.com/pytest-dev/pytest/issues/10840&gt;`_: pytest should no longer crash on AST with pathological position attributes, for example testing AST produced by `Hylang &lt;https://github.com/hylang/hy&gt;__`.


- `6267 &lt;https://github.com/pytest-dev/pytest/issues/6267&gt;`_: The full output of a test is no longer truncated if the truncation message would be longer than
the hidden text. The line number shown has also been fixed.



Bug Fixes
---------

- `10743 &lt;https://github.com/pytest-dev/pytest/issues/10743&gt;`_: The assertion rewriting mechanism now works correctly when assertion expressions contain the walrus operator.


- `10765 &lt;https://github.com/pytest-dev/pytest/issues/10765&gt;`_: Fixed :fixture:`tmp_path` fixture always raising :class:`OSError` on ``emscripten`` platform due to missing :func:`os.getuid`.


- `1904 &lt;https://github.com/pytest-dev/pytest/issues/1904&gt;`_: Correctly handle ``__tracebackhide__`` for chained exceptions.
NOTE: This change was reverted in version 7.3.1.



Improved Documentation
----------------------

- `10782 &lt;https://github.com/pytest-dev/pytest/issues/10782&gt;`_: Fixed the minimal example in :ref:`goodpractices`: ``pip install -e .`` requires a ``version`` entry in ``pyproject.toml`` to run successfully.



Trivial/Internal Changes
------------------------

- `10669 &lt;https://github.com/pytest-dev/pytest/issues/10669&gt;`_: pytest no longer directly depends on the `attrs &lt;https://www.attrs.org/en/stable/&gt;`__ package. While
we at pytest all love the package dearly and would like to thank the ``attrs`` team for many years of cooperation and support,
it makes sense for ``pytest`` to have as little external dependencies as possible, as this helps downstream projects.
With that in mind, we have replaced the pytest&#x27;s limited internal usage to use the standard library&#x27;s ``dataclasses`` instead.

Nice diffs for ``attrs`` classes are still supported though.

7.2.2

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

Bug Fixes
---------

- `10533 &lt;https://github.com/pytest-dev/pytest/issues/10533&gt;`_: Fixed :func:`pytest.approx` handling of dictionaries containing one or more values of `0.0`.


- `10592 &lt;https://github.com/pytest-dev/pytest/issues/10592&gt;`_: Fixed crash if `--cache-show` and `--help` are passed at the same time.


- `10597 &lt;https://github.com/pytest-dev/pytest/issues/10597&gt;`_: Fixed bug where a fixture method named ``teardown`` would be called as part of ``nose`` teardown stage.


- `10626 &lt;https://github.com/pytest-dev/pytest/issues/10626&gt;`_: Fixed crash if ``--fixtures`` and ``--help`` are passed at the same time.


- `10660 &lt;https://github.com/pytest-dev/pytest/issues/10660&gt;`_: Fixed :py:func:`pytest.raises` to return a &#x27;ContextManager&#x27; so that type-checkers could narrow
:code:`pytest.raises(...) if ... else nullcontext()` down to &#x27;ContextManager&#x27; rather than &#x27;object&#x27;.



Improved Documentation
----------------------

- `10690 &lt;https://github.com/pytest-dev/pytest/issues/10690&gt;`_: Added `CI` and `BUILD_NUMBER` environment variables to the documentation.


- `10721 &lt;https://github.com/pytest-dev/pytest/issues/10721&gt;`_: Fixed entry-points declaration in the documentation example using Hatch.


- `10753 &lt;https://github.com/pytest-dev/pytest/issues/10753&gt;`_: Changed wording of the module level skip to be very explicit
about not collecting tests and not executing the rest of the module.

7.2.1

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

Bug Fixes
---------

- `10452 &lt;https://github.com/pytest-dev/pytest/issues/10452&gt;`_: Fix &#x27;importlib.abc.TraversableResources&#x27; deprecation warning in Python 3.12.


- `10457 &lt;https://github.com/pytest-dev/pytest/issues/10457&gt;`_: If a test is skipped from inside a fixture, the test summary now shows the test location instead of the fixture location.


- `10506 &lt;https://github.com/pytest-dev/pytest/issues/10506&gt;`_: Fix bug where sometimes pytest would use the file system root directory as :ref:`rootdir &lt;rootdir&gt;` on Windows.


- `10607 &lt;https://github.com/pytest-dev/pytest/issues/10607&gt;`_: Fix a race condition when creating junitxml reports, which could occur when multiple instances of pytest execute in parallel.


- `10641 &lt;https://github.com/pytest-dev/pytest/issues/10641&gt;`_: Fix a race condition when creating or updating the stepwise plugin&#x27;s cache, which could occur when multiple xdist worker nodes try to simultaneously update the stepwise plugin&#x27;s cache.

7.2.0

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

Deprecations
------------

- `10012 &lt;https://github.com/pytest-dev/pytest/issues/10012&gt;`_: Update :class:`pytest.PytestUnhandledCoroutineWarning` to a deprecation; it will raise an error in pytest 8.


- `10396 &lt;https://github.com/pytest-dev/pytest/issues/10396&gt;`_: pytest no longer depends on the ``py`` library.  ``pytest`` provides a vendored copy of ``py.error`` and ``py.path`` modules but will use the ``py`` library if it is installed.  If you need other ``py.*`` modules, continue to install the deprecated ``py`` library separately, otherwise it can usually be removed as a dependency.


- `4562 &lt;https://github.com/pytest-dev/pytest/issues/4562&gt;`_: Deprecate configuring hook specs/impls using attributes/marks.

Instead use :py:func:`pytest.hookimpl` and :py:func:`pytest.hookspec`.
For more details, see the :ref:`docs &lt;legacy-path-hooks-deprecated&gt;`.


- `9886 &lt;https://github.com/pytest-dev/pytest/issues/9886&gt;`_: The functionality for running tests written for ``nose`` has been officially deprecated.

This includes:

* Plain ``setup`` and ``teardown`` functions and methods: this might catch users by surprise, as ``setup()`` and ``teardown()`` are not pytest idioms, but part of the ``nose`` support.
* Setup/teardown using the `with_setup &lt;with-setup-nose&gt;`_ decorator.

For more details, consult the :ref:`deprecation docs &lt;nose-deprecation&gt;`.

.. _`with-setup-nose`: https://nose.readthedocs.io/en/latest/testing_tools.html?highlight=with_setup#nose.tools.with_setup

- `7337 &lt;https://github.com/pytest-dev/pytest/issues/7337&gt;`_: A deprecation warning is now emitted if a test function returns something other than `None`. This prevents a common mistake among beginners that expect that returning a `bool` (for example `return foo(a, b) == result`) would cause a test to pass or fail, instead of using `assert`. The plan is to make returning non-`None` from tests an error in the future.


Features
--------

- `9897 &lt;https://github.com/pytest-dev/pytest/issues/9897&gt;`_: Added shell-style wildcard support to ``testpaths``.



Improvements
------------

- `10218 &lt;https://github.com/pytest-dev/pytest/issues/10218&gt;`_: ``pytest.mark.parametrize()`` (and similar functions) now accepts any ``Sequence[str]`` for the argument names,
instead of just ``list[str]`` and ``tuple[str, ...]``.

(Note that ``str``, which is itself a ``Sequence[str]``, is still treated as a
comma-delimited name list, as before).


- `10381 &lt;https://github.com/pytest-dev/pytest/issues/10381&gt;`_: The ``--no-showlocals`` flag has been added. This can be passed directly to tests to override ``--showlocals`` declared through ``addopts``.


- `3426 &lt;https://github.com/pytest-dev/pytest/issues/3426&gt;`_: Assertion failures with strings in NFC and NFD forms that normalize to the same string now have a dedicated error message detailing the issue, and their utf-8 representation is expressed instead.


- `8508 &lt;https://github.com/pytest-dev/pytest/issues/8508&gt;`_: Introduce multiline display for warning matching  via :py:func:`pytest.warns` and
enhance match comparison for :py:func:`pytest.ExceptionInfo.match` as returned by :py:func:`pytest.raises`.


- `8646 &lt;https://github.com/pytest-dev/pytest/issues/8646&gt;`_: Improve :py:func:`pytest.raises`. Previously passing an empty tuple would give a confusing
error. We now raise immediately with a more helpful message.


- `9741 &lt;https://github.com/pytest-dev/pytest/issues/9741&gt;`_: On Python 3.11, use the standard library&#x27;s :mod:`tomllib` to parse TOML.

`tomli` is no longer a dependency on Python 3.11.


- `9742 &lt;https://github.com/pytest-dev/pytest/issues/9742&gt;`_: Display assertion message without escaped newline characters with ``-vv``.


- `9823 &lt;https://github.com/pytest-dev/pytest/issues/9823&gt;`_: Improved error message that is shown when no collector is found for a given file.


- `9873 &lt;https://github.com/pytest-dev/pytest/issues/9873&gt;`_: Some coloring has been added to the short test summary.


- `9883 &lt;https://github.com/pytest-dev/pytest/issues/9883&gt;`_: Normalize the help description of all command-line options.


- `9920 &lt;https://github.com/pytest-dev/pytest/issues/9920&gt;`_: Display full crash messages in ``short test summary info``, when running in a CI environment.


- `9987 &lt;https://github.com/pytest-dev/pytest/issues/9987&gt;`_: Added support for hidden configuration file by allowing ``.pytest.ini`` as an alternative to ``pytest.ini``.



Bug Fixes
---------

- `10150 &lt;https://github.com/pytest-dev/pytest/issues/10150&gt;`_: :data:`sys.stdin` now contains all expected methods of a file-like object when capture is enabled.


- `10382 &lt;https://github.com/pytest-dev/pytest/issues/10382&gt;`_: Do not break into pdb when ``raise unittest.SkipTest()`` appears top-level in a file.


- `7792 &lt;https://github.com/pytest-dev/pytest/issues/7792&gt;`_: Marks are now inherited according to the full MRO in test classes. Previously, if a test class inherited from two or more classes, only marks from the first super-class would apply.

When inheriting marks from super-classes, marks from the sub-classes are now ordered before marks from the super-classes, in MRO order. Previously it was the reverse.

When inheriting marks from super-classes, the `pytestmark` attribute of the sub-class now only contains the marks directly applied to it. Previously, it also contained marks from its super-classes. Please note that this attribute should not normally be accessed directly; use :func:`Node.iter_markers &lt;_pytest.nodes.Node.iter_markers&gt;` instead.


- `9159 &lt;https://github.com/pytest-dev/pytest/issues/9159&gt;`_: Showing inner exceptions by forcing native display in ``ExceptionGroups`` even when using display options other than ``--tb=native``. A temporary step before full implementation of pytest-native display for inner exceptions in ``ExceptionGroups``.


- `9877 &lt;https://github.com/pytest-dev/pytest/issues/9877&gt;`_: Ensure ``caplog.get_records(when)`` returns current/correct data after invoking ``caplog.clear()``.



Improved Documentation
----------------------

- `10344 &lt;https://github.com/pytest-dev/pytest/issues/10344&gt;`_: Update information on writing plugins to use ``pyproject.toml`` instead of ``setup.py``.


- `9248 &lt;https://github.com/pytest-dev/pytest/issues/9248&gt;`_: The documentation is now built using Sphinx 5.x (up from 3.x previously).


- `9291 &lt;https://github.com/pytest-dev/pytest/issues/9291&gt;`_: Update documentation on how :func:`pytest.warns` affects :class:`DeprecationWarning`.



Trivial/Internal Changes
------------------------

- `10313 &lt;https://github.com/pytest-dev/pytest/issues/10313&gt;`_: Made ``_pytest.doctest.DoctestItem`` export ``pytest.DoctestItem`` for
type check and runtime purposes. Made `_pytest.doctest` use internal APIs
to avoid circular imports.


- `9906 &lt;https://github.com/pytest-dev/pytest/issues/9906&gt;`_: Made ``_pytest.compat`` re-export ``importlib_metadata`` in the eyes of type checkers.


- `9910 &lt;https://github.com/pytest-dev/pytest/issues/9910&gt;`_: Fix default encoding warning (``EncodingWarning``) in ``cacheprovider``


- `9984 &lt;https://github.com/pytest-dev/pytest/issues/9984&gt;`_: Improve the error message when we attempt to access a fixture that has been
torn down.
Add an additional sentence to the docstring explaining when it&#x27;s not a good
idea to call ``getfixturevalue``.

7.1.3

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

Bug Fixes
---------

- `10060 &lt;https://github.com/pytest-dev/pytest/issues/10060&gt;`_: When running with ``--pdb``, ``TestCase.tearDown`` is no longer called for tests when the *class* has been skipped via ``unittest.skip`` or ``pytest.mark.skip``.


- `10190 &lt;https://github.com/pytest-dev/pytest/issues/10190&gt;`_: Invalid XML characters in setup or teardown error messages are now properly escaped for JUnit XML reports.


- `10230 &lt;https://github.com/pytest-dev/pytest/issues/10230&gt;`_: Ignore ``.py`` files created by ``pyproject.toml``-based editable builds introduced in `pip 21.3 &lt;https://pip.pypa.io/en/stable/news/#v21-3&gt;`__.


- `3396 &lt;https://github.com/pytest-dev/pytest/issues/3396&gt;`_: Doctests now respect the ``--import-mode`` flag.


- `9514 &lt;https://github.com/pytest-dev/pytest/issues/9514&gt;`_: Type-annotate ``FixtureRequest.param`` as ``Any`` as a stop gap measure until :issue:`8073` is fixed.


- `9791 &lt;https://github.com/pytest-dev/pytest/issues/9791&gt;`_: Fixed a path handling code in ``rewrite.py`` that seems to work fine, but was incorrect and fails in some systems.


- `9917 &lt;https://github.com/pytest-dev/pytest/issues/9917&gt;`_: Fixed string representation for :func:`pytest.approx` when used to compare tuples.



Improved Documentation
----------------------

- `9937 &lt;https://github.com/pytest-dev/pytest/issues/9937&gt;`_: Explicit note that :fixture:`tmpdir` fixture is discouraged in favour of :fixture:`tmp_path`.



Trivial/Internal Changes
------------------------

- `10114 &lt;https://github.com/pytest-dev/pytest/issues/10114&gt;`_: Replace `atomicwrites &lt;https://github.com/untitaker/python-atomicwrites&gt;`__ dependency on windows with `os.replace`.

7.1.2

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

Bug Fixes
---------

- `9726 &lt;https://github.com/pytest-dev/pytest/issues/9726&gt;`_: An unnecessary ``numpy`` import inside :func:`pytest.approx` was removed.


- `9820 &lt;https://github.com/pytest-dev/pytest/issues/9820&gt;`_: Fix comparison of  ``dataclasses`` with ``InitVar``.


- `9869 &lt;https://github.com/pytest-dev/pytest/issues/9869&gt;`_: Increase ``stacklevel`` for the ``NODE_CTOR_FSPATH_ARG`` deprecation to point to the
user&#x27;s code, not pytest.


- `9871 &lt;https://github.com/pytest-dev/pytest/issues/9871&gt;`_: Fix a bizarre (and fortunately rare) bug where the `temp_path` fixture could raise
an internal error while attempting to get the current user&#x27;s username.

7.1.1

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

Bug Fixes
---------

- `9767 &lt;https://github.com/pytest-dev/pytest/issues/9767&gt;`_: Fixed a regression in pytest 7.1.0 where some conftest.py files outside of the source tree (e.g. in the `site-packages` directory) were not picked up.

7.1.0

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

Breaking Changes
----------------

- `8838 &lt;https://github.com/pytest-dev/pytest/issues/8838&gt;`_: As per our policy, the following features have been deprecated in the 6.X series and are now
removed:

* ``pytest._fillfuncargs`` function.

* ``pytest_warning_captured`` hook - use ``pytest_warning_recorded`` instead.

* ``-k -foobar`` syntax - use ``-k &#x27;not foobar&#x27;`` instead.

* ``-k foobar:`` syntax.

* ``pytest.collect`` module - import from ``pytest`` directly.

For more information consult
`Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__ in the docs.


- `9437 &lt;https://github.com/pytest-dev/pytest/issues/9437&gt;`_: Dropped support for Python 3.6, which reached `end-of-life &lt;https://devguide.python.org/#status-of-python-branches&gt;`__ at 2021-12-23.



Improvements
------------

- `5192 &lt;https://github.com/pytest-dev/pytest/issues/5192&gt;`_: Fixed test output for some data types where ``-v`` would show less information.

Also, when showing diffs for sequences, ``-q`` would produce full diffs instead of the expected diff.


- `9362 &lt;https://github.com/pytest-dev/pytest/issues/9362&gt;`_: pytest now avoids specialized assert formatting when it is detected that the default ``__eq__`` is overridden in ``attrs`` or ``dataclasses``.


- `9536 &lt;https://github.com/pytest-dev/pytest/issues/9536&gt;`_: When ``-vv`` is given on command line, show skipping and xfail reasons in full instead of truncating them to fit the terminal width.


- `9644 &lt;https://github.com/pytest-dev/pytest/issues/9644&gt;`_: More information about the location of resources that led Python to raise :class:`ResourceWarning` can now
be obtained by enabling :mod:`tracemalloc`.

See :ref:`resource-warnings` for more information.


- `9678 &lt;https://github.com/pytest-dev/pytest/issues/9678&gt;`_: More types are now accepted in the ``ids`` argument to ``pytest.mark.parametrize``.
Previously only `str`, `float`, `int` and `bool` were accepted;
now `bytes`, `complex`, `re.Pattern`, `Enum` and anything with a `__name__` are also accepted.


- `9692 &lt;https://github.com/pytest-dev/pytest/issues/9692&gt;`_: :func:`pytest.approx` now raises a :class:`TypeError` when given an unordered sequence (such as :class:`set`).

Note that this implies that custom classes which only implement ``__iter__`` and ``__len__`` are no longer supported as they don&#x27;t guarantee order.



Bug Fixes
---------

- `8242 &lt;https://github.com/pytest-dev/pytest/issues/8242&gt;`_: The deprecation of raising :class:`unittest.SkipTest` to skip collection of
tests during the pytest collection phase is reverted - this is now a supported
feature again.


- `9493 &lt;https://github.com/pytest-dev/pytest/issues/9493&gt;`_: Symbolic link components are no longer resolved in conftest paths.
This means that if a conftest appears twice in collection tree, using symlinks, it will be executed twice.
For example, given

   tests/real/conftest.py
   tests/real/test_it.py
   tests/link -&gt; tests/real

running ``pytest tests`` now imports the conftest twice, once as ``tests/real/conftest.py`` and once as ``tests/link/conftest.py``.
This is a fix to match a similar change made to test collection itself in pytest 6.0 (see :pull:`6523` for details).


- `9626 &lt;https://github.com/pytest-dev/pytest/issues/9626&gt;`_: Fixed count of selected tests on terminal collection summary when there were errors or skipped modules.

If there were errors or skipped modules on collection, pytest would mistakenly subtract those from the selected count.


- `9645 &lt;https://github.com/pytest-dev/pytest/issues/9645&gt;`_: Fixed regression where ``--import-mode=importlib`` used together with :envvar:`PYTHONPATH` or :confval:`pythonpath` would cause import errors in test suites.


- `9708 &lt;https://github.com/pytest-dev/pytest/issues/9708&gt;`_: :fixture:`pytester` now requests a :fixture:`monkeypatch` fixture instead of creating one internally. This solves some issues with tests that involve pytest environment variables.


- `9730 &lt;https://github.com/pytest-dev/pytest/issues/9730&gt;`_: Malformed ``pyproject.toml`` files now produce a clearer error message.

7.0.1

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

Bug Fixes
---------

- `9608 &lt;https://github.com/pytest-dev/pytest/issues/9608&gt;`_: Fix invalid importing of ``importlib.readers`` in Python 3.9.


- `9610 &lt;https://github.com/pytest-dev/pytest/issues/9610&gt;`_: Restore `UnitTestFunction.obj` to return unbound rather than bound method.
Fixes a crash during a failed teardown in unittest TestCases with non-default `__init__`.
Regressed in pytest 7.0.0.


- `9636 &lt;https://github.com/pytest-dev/pytest/issues/9636&gt;`_: The ``pythonpath`` plugin was renamed to ``python_path``. This avoids a conflict with the ``pytest-pythonpath`` plugin.


- `9642 &lt;https://github.com/pytest-dev/pytest/issues/9642&gt;`_: Fix running tests by id with ``::`` in the parametrize portion.


- `9643 &lt;https://github.com/pytest-dev/pytest/issues/9643&gt;`_: Delay issuing a :class:`~pytest.PytestWarning` about diamond inheritance involving :class:`~pytest.Item` and
:class:`~pytest.Collector` so it can be filtered using :ref:`standard warning filters &lt;warnings&gt;`.

7.0.0

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

(**Please see the full set of changes for this release also in the 7.0.0rc1 notes below**)

Deprecations
------------

- `9488 &lt;https://github.com/pytest-dev/pytest/issues/9488&gt;`_: If custom subclasses of nodes like :class:`pytest.Item` override the
``__init__`` method, they should take ``**kwargs``. See
:ref:`uncooperative-constructors-deprecated` for details.

Note that a deprection warning is only emitted when there is a conflict in the
arguments pytest expected to pass. This deprecation was already part of pytest
7.0.0rc1 but wasn&#x27;t documented.



Bug Fixes
---------

- `9355 &lt;https://github.com/pytest-dev/pytest/issues/9355&gt;`_: Fixed error message prints function decorators when using assert in Python 3.8 and above.


- `9396 &lt;https://github.com/pytest-dev/pytest/issues/9396&gt;`_: Ensure `pytest.Config.inifile` is available during the :hook:`pytest_cmdline_main` hook (regression during ``7.0.0rc1``).



Improved Documentation
----------------------

- `9404 &lt;https://github.com/pytest-dev/pytest/issues/9404&gt;`_: Added extra documentation on alternatives to common misuses of `pytest.warns(None)` ahead of its deprecation.


- `9505 &lt;https://github.com/pytest-dev/pytest/issues/9505&gt;`_: Clarify where the configuration files are located. To avoid confusions documentation mentions
that configuration file is located in the root of the repository.



Trivial/Internal Changes
------------------------

- `9521 &lt;https://github.com/pytest-dev/pytest/issues/9521&gt;`_: Add test coverage to assertion rewrite path.

7.0.0rc1

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

Breaking Changes
----------------

- `7259 &lt;https://github.com/pytest-dev/pytest/issues/7259&gt;`_: The :ref:`Node.reportinfo() &lt;non-python tests&gt;` function first return value type has been expanded from `py.path.local | str` to `os.PathLike[str] | str`.

Most plugins which refer to `reportinfo()` only define it as part of a custom :class:`pytest.Item` implementation.
Since `py.path.local` is an `os.PathLike[str]`, these plugins are unaffacted.

Plugins and users which call `reportinfo()`, use the first return value and interact with it as a `py.path.local`, would need to adjust by calling `py.path.local(fspath)`.
Although preferably, avoid the legacy `py.path.local` and use `pathlib.Path`, or use `item.location` or `item.path`, instead.

Note: pytest was not able to provide a deprecation period for this change.


- `8246 &lt;https://github.com/pytest-dev/pytest/issues/8246&gt;`_: ``--version`` now writes version information to ``stdout`` rather than ``stderr``.


- `8733 &lt;https://github.com/pytest-dev/pytest/issues/8733&gt;`_: Drop a workaround for `pyreadline &lt;https://github.com/pyreadline/pyreadline&gt;`__ that made it work with ``--pdb``.

The workaround was introduced in `1281 &lt;https://github.com/pytest-dev/pytest/pull/1281&gt;`__ in 2015, however since then
`pyreadline seems to have gone unmaintained &lt;https://github.com/pyreadline/pyreadline/issues/58&gt;`__, is `generating
warnings &lt;https://github.com/pytest-dev/pytest/issues/8847&gt;`__, and will stop working on Python 3.10.


- `9061 &lt;https://github.com/pytest-dev/pytest/issues/9061&gt;`_: Using :func:`pytest.approx` in a boolean context now raises an error hinting at the proper usage.

It is apparently common for users to mistakenly use ``pytest.approx`` like this:

.. code-block:: python

   assert pytest.approx(actual, expected)

While the correct usage is:

.. code-block:: python

   assert actual == pytest.approx(expected)

The new error message helps catch those mistakes.


- `9277 &lt;https://github.com/pytest-dev/pytest/issues/9277&gt;`_: The ``pytest.Instance`` collector type has been removed.
Importing ``pytest.Instance`` or ``_pytest.python.Instance`` returns a dummy type and emits a deprecation warning.
See :ref:`instance-collector-deprecation` for details.


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

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

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

In the pytest ``7.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.PytestRemovedIn7Warning

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

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



Deprecations
------------

- `7259 &lt;https://github.com/pytest-dev/pytest/issues/7259&gt;`_: ``py.path.local`` arguments for hooks have been deprecated. See :ref:`the deprecation note &lt;legacy-path-hooks-deprecated&gt;` for full details.

``py.path.local`` arguments to Node constructors have been deprecated. See :ref:`the deprecation note &lt;node-ctor-fspath-deprecation&gt;` for full details.

.. note::
   The name of the :class:`~_pytest.nodes.Node` arguments and attributes (the
   new attribute being ``path``) is **the opposite** of the situation for hooks
   (the old argument being ``path``).

   This is an unfortunate artifact due to historical reasons, which should be
   resolved in future versions as we slowly get rid of the :pypi:`py`
   dependency (see :issue:`9283` for a longer discussion).


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: Directly constructing the following classes is now deprecated:

- ``_pytest.mark.structures.Mark``
- ``_pytest.mark.structures.MarkDecorator``
- ``_pytest.mark.structures.MarkGenerator``
- ``_pytest.python.Metafunc``
- ``_pytest.runner.CallInfo``
- ``_pytest._code.ExceptionInfo``
- ``_pytest.config.argparsing.Parser``
- ``_pytest.config.argparsing.OptionGroup``
- ``_pytest.pytester.HookRecorder``

These constructors have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 8.


- `8242 &lt;https://github.com/pytest-dev/pytest/issues/8242&gt;`_: Raising :class:`unittest.SkipTest` to skip collection of tests during the
pytest collection phase is deprecated. Use :func:`pytest.skip` instead.

Note: This deprecation only relates to using :class:`unittest.SkipTest` during test
collection. You are probably not doing that. Ordinary usage of
:class:`unittest.SkipTest` / :meth:`unittest.TestCase.skipTest` /
:func:`unittest.skip` in unittest test cases is fully supported.

.. note:: This deprecation has been reverted in pytest 7.1.0.


- `8315 &lt;https://github.com/pytest-dev/pytest/issues/8315&gt;`_: Several behaviors of :meth:`Parser.addoption &lt;pytest.Parser.addoption&gt;` are now
scheduled for removal in pytest 8 (deprecated since pytest 2.4.0):

- ``parser.addoption(..., help=&quot;.. %default ..&quot;)`` - use ``%(default)s`` instead.
- ``parser.addoption(..., type=&quot;int/string/float/complex&quot;)`` - use ``type=int`` etc. instead.


- `8447 &lt;https://github.com/pytest-dev/pytest/issues/8447&gt;`_: Defining a custom pytest node type which is both an :class:`~pytest.Item` and a :class:`~pytest.Collector` (e.g. :class:`~pytest.File`) now issues a warning.
It was never sanely supported and triggers hard to debug errors.

See :ref:`the deprecation note &lt;diamond-inheritance-deprecated&gt;` for full details.


- `8592 &lt;https://github.com/pytest-dev/pytest/issues/8592&gt;`_: ``pytest_cmdline_preparse`` has been officially deprecated.  It will be removed in a future release.  Use :hook:`pytest_load_initial_conftests` instead.

See :ref:`the deprecation note &lt;cmdline-preparse-deprecated&gt;` for full details.


- `8645 &lt;https://github.com/pytest-dev/pytest/issues/8645&gt;`_: :func:`pytest.warns(None) &lt;pytest.warns&gt;` is now deprecated because many people used
it to mean &quot;this code does not emit warnings&quot;, but it actually had the effect of
checking that the code emits at least one warning of any type - like ``pytest.warns()``
or ``pytest.warns(Warning)``.


- `8948 &lt;https://github.com/pytest-dev/pytest/issues/8948&gt;`_: :func:`pytest.skip(msg=...) &lt;pytest.skip&gt;`, :func:`pytest.fail(msg=...) &lt;pytest.fail&gt;` and :func:`pytest.exit(msg=...) &lt;pytest.exit&gt;`
signatures now accept a ``reason`` argument instead of ``msg``.  Using ``msg`` still works, but is deprecated and will be removed in a future release.

This was changed for consistency with :func:`pytest.mark.skip &lt;pytest.mark.skip&gt;` and  :func:`pytest.mark.xfail &lt;pytest.mark.xfail&gt;` which both accept
``reason`` as an argument.

- `8174 &lt;https://github.com/pytest-dev/pytest/issues/8174&gt;`_: The following changes have been made to types reachable through :attr:`pytest.ExceptionInfo.traceback`:

- The ``path`` property of ``_pytest.code.Code`` returns ``Path`` instead of ``py.path.local``.
- The ``path`` property of ``_pytest.code.TracebackEntry`` returns ``Path`` instead of ``py.path.local``.

There was no deprecation period for this change (sorry!).


Features
--------

- `5196 &lt;https://github.com/pytest-dev/pytest/issues/5196&gt;`_: Tests are now ordered by definition order in more cases.

In a class hierarchy, tests from base classes are now consistently ordered before tests defined on their subclasses (reverse MRO order).


- `7132 &lt;https://github.com/pytest-dev/pytest/issues/7132&gt;`_: Added two environment variables :envvar:`PYTEST_THEME` and :envvar:`PYTEST_THEME_MODE` to let the users customize the pygments theme used.


- `7259 &lt;https://github.com/pytest-dev/pytest/issues/7259&gt;`_: Added :meth:`cache.mkdir() &lt;pytest.Cache.mkdir&gt;`, which is similar to the existing ``cache.makedir()``,
but returns a :class:`pathlib.Path` instead of a legacy ``py.path.local``.

Added a ``paths`` type to :meth:`parser.addini() &lt;pytest.Parser.addini&gt;`,
as in ``parser.addini(&quot;mypaths&quot;, &quot;my paths&quot;, type=&quot;paths&quot;)``,
which is similar to the existing ``pathlist``,
but returns a list of :class:`pathlib.Path` instead of legacy ``py.path.local``.


- `7469 &lt;htt

pyup-bot · 2024-02-17T17:14:15Z

Closing this in favor of #326

Update pytest from 3.8.2 to 8.0.0

e71ff56

pyup-bot mentioned this pull request Jan 28, 2024

Update pytest to 7.4.4 #323

Closed

pyup-bot closed this Feb 17, 2024

pydanny deleted the pyup-update-pytest-3.8.2-to-8.0.0 branch February 17, 2024 17:14

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update pytest to 8.0.0 #325

Update pytest to 8.0.0 #325

pyup-bot commented Jan 28, 2024

pyup-bot commented Feb 17, 2024

Update pytest to 8.0.0 #325

Update pytest to 8.0.0 #325

Conversation

pyup-bot commented Jan 28, 2024

8.0.0

8.0.0rc2

8.0.0rc1

7.4.4

7.4.3

7.4.2

7.4.1

7.4.0

7.3.2

7.3.1

7.3.0

7.2.2

7.2.1

7.2.0

7.1.3

7.1.2

7.1.1

7.1.0

7.0.1

7.0.0

7.0.0rc1

pyup-bot commented Feb 17, 2024