BlazingNeutron/wyoming-whisper-api-client

Watch

Fork 0

Update dependency pytest to v9 #15

Closed

renovate-bot wants to merge 1 commit from renovate/pytest-9.x into main

renovate-bot commented

2026-10-29 15:10:19 -04:00

Collaborator

This PR contains the following updates:

Package	Update	Change
pytest (changelog)	major	`==7.4.4` → `==9.2.0`

Release Notes

pytest-dev/pytest (pytest)

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

#14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.
#8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.
#993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:
- a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
- a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.
pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

#14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec.
The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.
#14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.
#14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1,
all higher-scoped fixtures (module, package, and session) defined
as instance methods are now deprecated.

They suffer from the same issue the original deprecation only fixed for
class-scoped fixtures, see 10819 and 14011.
#14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.
#7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

#14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
#2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
#6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

#10745: A RecursionError whose recursion origin cannot be located now shows only the
first and last 10 stack frames, matching what pytest already did when locating
the origin failed outright. Previously the full traceback -- often around a
thousand near-identical frames -- was rendered, which was both slow and
unreadable. Pass --full-trace to see every frame.
#10745: The line numbers of a module's statements are now computed once per traceback
instead of once per traceback entry, which noticeably speeds up rendering
failures raised from large test modules.
#11418: The cached rewritten modules in __pycache__ are now invalidated by a hash of
the source instead of its modification time, using the checked-hash pyc format
from 552.

Timestamps make the cache useless wherever source files get fresh modification
times, most notably in CI: a checkout gives every file a new mtime, so a
restored cache is discarded in full and every test module is rewritten again.
Hashing the source costs roughly 15 microseconds per file and makes the cache
survive that.

Existing timestamp based caches are ignored and rewritten once.
#12624: The pytest_plugins variable and the PYTEST_PLUGINS environment variable now also accept entry point names of installed plugins (e.g. xdist), in addition to importable module names, matching the behavior of the -p command-line option.

As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the plugins: line of the terminal header (12615).

Based on the original implementation by Marcel Telka in 12616.
#12697: Warnings emitted while importing plugins through -p, PYTEST_PLUGINS, or entry point autoloading are now captured, filtered, and reported like other warnings.
#12860: Assertion diffs for dict.items() and dict.keys() comparisons (>=, <=, >, <, ==) now show which items are missing, the same way set comparisons do.
#13354: Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> now also accepts a ~pytest.MarkDecorator as its default, for example item.get_closest_marker("foo", pytest.mark.foo(1)), and returns the wrapped ~pytest.Mark.

Previously the only way to build a default was to instantiate ~pytest.Mark directly, which is private and warns.
#13369: Improved the error from pytest.RunResult.assert_outcomes when a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins.
#13431: Exposed pytest.ParameterSet as the type of the return value of pytest.param().
This can be used in type annotations and isinstance checks.
#13564: Issue a warning when fixtures are wrapped with a decorator that prevents
correct discovery, including @classmethod above @pytest.fixture and
@staticmethod above @pytest.fixture. Put @pytest.fixture above
those decorators on test classes.
#14164: Exposed pytest.Approx as the type of the return value of pytest.approx().
This can be used in type annotations and isinstance checks.
#14463: Assertion diffs for mappings now match up keys the way the compared mappings match them themselves.

Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping
with its own notion of key equivalence, such as case-insensitive header mappings, no longer
reports its common keys as missing on either side.
#14523: Large assertion comparison diffs are now built lazily and capped to the
truncation budget, so a huge diff is no longer formatted in full just to
be truncated. As a consequence, the truncation footer no longer
reports the exact number of hidden lines.
#14687: The default fd-level output capturing (--capture=fd) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites.
#14724: --no-summary now only applies directly to pytest's own summary.

The flag no longer skips the pytest_terminal_summary hook, so third-party
plugins (for example coverage) can still write their terminal summaries.
#14751: parser.addini <pytest.Parser.addini> now also accepts type expressions for its type argument, in addition to the existing string tags: the plain Python types str, bool, int, float, a Literal of strings, and unions of these (for example int | str or int | Literal["auto"]).
#14754: pytest.approx() now rejects infinite relative tolerances for datetime.timedelta values with a clear ValueError instead of raising OverflowError.
#14791: The junit_family, junit_logging, junit_duration_report, console_output_style, empty_parameter_set_mark, assertion_text_diff_style and tmp_path_retention_policy configuration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, and pytest --help lists the accepted values.

config.getini <pytest.Config.getini> now raises pytest.UsageError instead of TypeError or ValueError when the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raises ValueError.
#15006: pytest.approx now emits pytest.PytestApproxDecimalToleranceWarning when a rel or abs tolerance is given as a float that cannot be represented exactly for a ~decimal.Decimal comparison, since such a tolerance is widened to the float's exact binary value.
#14675, #14953, #15153, #15132: The truncation_limit_lines, truncation_limit_chars, max_warnings, verbosity_assertions, verbosity_test_cases, verbosity_subtests, tmp_path_retention_count, log_level, log_cli_level, log_file_level,log_auto_indent and faulthandler_timeout configuration options now accept native integer (and, for log_auto_indent, boolean) values in TOML configuration files, while still accepting strings for backward compatibility.
log_file_mode now reports invalid values as a usage error.
#15254: tmp_path and TempPathFactory.mktemp <pytest.TempPathFactory.mktemp> no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist.
#4569: Node.add_marker <_pytest.nodes.Node.add_marker> now stores a ~pytest.Mark in node.keywords, matching what marks applied during collection store. Previously it stored a ~pytest.MarkDecorator.
#9436: Avoided formatting tracebacks for tests marked with xfail(run=False).

Bug fixes

#10128: Configured warning filters now apply to warnings emitted by pytest_configure hooks.
#10210: pytest.approx now raises a TypeError for any nested container, not
only for one of the same type as its parent. Previously approx([{"k": 1}])
and approx({"k": [1]}) were accepted and then compared unequal to every
value, silently ignoring the tolerance, while approx([[1]]) correctly
reported that nesting is unsupported.
#10644: monkeypatch.setattr() no longer leaves a new entry in the instance __dict__ when it patches an attribute that the instance inherits from its class.

Previously undo() assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically.
#1139: Fixed tracebacks showing ??? instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root.
The source lookup now falls back to searching sys.path for such filenames, as the standard traceback module does.
#11502: The rootdir is no longer derived from a configuration file that is not a regular file, such as --config-file=/dev/null.
#11783: Plugins installed in editable mode (660) are marked for assertion rewriting again.

Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case.
#11933: pytest.warns no longer re-emits unmatched warnings with module="warnings", which caused module-based warning filters to be applied to the wrong warnings. Since warnings.WarningMessage does not record the module a warning was emitted with, re-emitted warnings now use the standard warnings.warn_explicit default of deriving the module from the warning's filename.
#12175: ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly> now strips the AssertionError: prefix of failed assert statements for ~pytest.ExceptionInfo objects created by pytest.raises, and failures inside unittest.TestCase.subTest report the same short crash line as regular tests.
#12223: The message attribute of <failure> and <error> elements in --junitxml reports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with -vv) produced attributes tens of thousands of characters long, which some XML parsers fail on.
#12307: Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in assert condition, msg) when using -vv: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with ....
#12824: Custom command-line options now fail with a clear error when their implicit
destination conflicts with an existing option, avoiding silent overrides of
built-in options such as -k.
#13292: Fixed a stale rewritten module being used when a test file is modified twice
within the same second without changing its size -- the pyc header could only
record whole-second timestamps. The cache is now keyed on a hash of the source.
#14036: __tracebackhide__ is now respected in ExceptionGroup tracebacks, both for the group itself and for its sub-exceptions.
#14189: Nested usage of caplog.filtering <pytest.LogCaptureFixture.filtering> no longer removes filters early if they were already present.
#14412: Fixed incorrect timing information for subtests and parent tests when console_output_style = "times".
#14445: Assertion rewriting no longer evaluates walrus operator (:=) expressions more than once, which reported results the test never computed when the expression had side effects.

An operand evaluated before a later walrus is now reported with the value it actually saw, so assert value != identity(value := value.lower()) keeps Python's left-to-right order.
#14552: Fixed stale co_filename values after a test module or directory is moved. Assertion-rewrite caches are reused when the source hash still matches, and in-memory code objects are pointed at the current path.
#14586: Negative values passed to log_auto_indent now correctly fall back to no indentation, matching the documented behavior.
#14619: Fixed a crash in pytest.mark.parametrize when a non-sequence value is passed for a parameter set. It now provides a clear error message during collection.
#14635: Fixed fixture resolution failures when specifying multiple test paths on the command line that share common parent directories. Parametrized fixtures defined in a conftest.py could be silently dropped depending on the order of the specified paths.
#14637: Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning.
#14638: Top-level options in pytest.toml and .pytest.toml files now raise an error instead of being silently ignored when no [pytest] table is present.
#14683: Fixed a regression in pytest 9.1 where a conftest.py located in the rootdir was no longer visible to tests and doctests collected from outside the rootdir (for example when passing a parent directory of the rootdir as a collection argument, or setting --rootdir to a subdirectory).

As a result, fixtures defined in such a conftest -- including doctest_namespace injections -- were not available, causing errors such as NameError in doctests.
#14700: Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped.
#14705: TOML configuration files passed via -c now also read their configuration from the [pytest] table, the one pytest's own configuration files use. The [tool.pytest] and [tool.pytest.ini_options] tables such files were previously restricted to keep working; using both styles in one file is an error.
#14828: Exception groups raised from another exception now print their cause chain only once in the traceback output.
#14864: Fixed collection on Windows collecting the whole suite instead of the given path, on file systems which do not support file IDs (st_ino is 0 for every file, as seen for example on sshfs-win/WinFsp mounts).
#14884: Cache.get(), Cache.set() and Cache.mkdir() now reject keys that resolve outside the cache directory, and --cache-show ignores glob matches outside it.
#14909: Fixed MonkeyPatch.delattr <pytest.MonkeyPatch.delattr>, MonkeyPatch.setitem <pytest.MonkeyPatch.setitem> and MonkeyPatch.delitem <pytest.MonkeyPatch.delitem> recording a stale undo entry when the underlying mutation failed, which could cause spurious errors during teardown. The undo entry is now recorded only after the mutation succeeds, matching the behavior of MonkeyPatch.setattr <pytest.MonkeyPatch.setattr>.
#14912: ~pytest.PytestWarning instances defined in _pytest.deprecated are no longer reused across warnings.warn calls, so warnings raised as errors (e.g. with -W error) no longer accumulate stale traceback frames from previous raises.
#14942: Fixed a regression in 9.1.0 that made collection very slow (quadratic) when many fixtures are defined with the same name.
This can happen particularly when many tests are defined in separate classes which inherit from a base class which defines fixtures (the fixtures are repeated per class).
#15005: pytest.approx no longer treats finite ~decimal.Decimal values outside the float range (such as Decimal("1e400")) as infinite, which made in-tolerance comparisons fail.
#15006: Restored the tolerance shown by pytest.approx for ~decimal.Decimal values, which since 9.0 displayed ??? for the default tolerance and reported the raw rel ratio instead of the absolute tolerance actually compared against.
#15006: The failure message for pytest.approx comparisons of ~decimal.Decimal collections no longer reports Max absolute difference: -inf, or crashes for mappings, when the decimal.FloatOperation trap is set.
#15006: pytest.approx no longer raises AttributeError when comparing numpy.ndarray instances with object dtype, such as arrays of ~decimal.Decimal.
#15032: Help texts for command-line options and configuration options now keep their indentation
and blank lines. Previously each line was stripped before wrapping, so a wrapped
list item was indistinguishable from a new one and blank lines were dropped; configuration
option help lost its line breaks entirely.
#15043: Cache writes now emit pytest.PytestCacheWarning when writing or closing the cache file fails, consistent with errors opening the file.
#15052: Fixed possible off-by-one line numbers in --fixtures and --fixtures-per-test output.
#15145: With console_output_style set to times, durations just below a unit boundary are now shown in the next unit (e.g. 1.000ms instead of 1000.0us).
#15172: Assertion diffs now pretty-print the built-in frozendict (Python 3.15+) across multiple lines, similarly to how dict is displayed.
#4569: -k no longer matches attributes that end up in a test function's __dict__ without being meant as keywords, such as pytest's own pytestmark attribute and the bookkeeping left behind by functools.wraps and functools.lru_cache.
#6750: Fix fixture argument discovery for custom collectors that pass bound methods to pytest.Function.
#6997: XFAIL reports from teardown phases now include the phase in the short test
summary.
#7940: Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed.
#8321: Fixed exception chains being duplicated in the traceback output when an exception in the chain (__cause__/__context__) has no traceback of its own, and that exception is itself linked to further exceptions.
#8914: Tests parametrized with higher-than-function scope are now reordered by
parameter value rather than by parameter index, so that items using equal
parameter values are grouped together and share a single fixture setup, even
when they are parametrized by separate @pytest.mark.parametrize <pytest.mark.parametrize ref>
calls. Previously, an expensive higher-scoped fixture could be set up and torn
down repeatedly for the same parameter value.

Unhashable parameter values (e.g. dicts) keep the previous index-based
grouping behavior.

As a consequence, the order in which parametrized tests run may change
(fixture setup/teardown counts can only decrease, not increase).
#9924: Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure.

Improved documentation

#10721: Replaced setup.py usage with pyproject.toml in writing-plugins.
#12658: Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation.
#12857: Documented how --confcutdir affects initial conftest.py discovery.
#14157: Added the pytest-flakefighters plugin to the list of flaky test plugins in plugins.rst.
Added flaky test papers published on the Test FLARE project to the list of flaky papers in plugins.rst.
#15127: Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type.
#15242: The installation instructions <installation> and install-package-with-pip now show how to install pytest into a virtual environment with venv and pip, uv or virtualenv, and explain the externally-managed-environment error.
#4569: pytest --help, the -k reference entry and select-tests no longer describe -k as a Python expression matched against test names only; keyword expressions now shows marker names being matched as well. The examples that looked up a marker use Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> rather than item.keywords.
#9614: Clarified that session.items and session.testscollected exclude deselected tests in the pytest_collection documentation.

Packaging updates and notes for downstreams

#11680: Source archives of arbitrary commits -- the tarballs GitHub serves under
/archive/, not just the ones for tags -- can now be built into an sdist or a
wheel with a correct version. A .git_archival.txt file, expanded by git archive via export-subst, carries the describe output that
setuptools-scm would otherwise have to ask git for.

The archival file deliberately omits ref-names. Recording it would make the
content of an archive -- and therefore its checksum -- change whenever a branch
that points at the archived commit is moved afterwards, which is how the
equivalent tarballs of tagged releases became unstable for other projects.
Describe output alone depends only on the commit and on the tags reachable from
it.

The archival file is not shipped in the sdist -- an sdist carries its version
in its metadata, and the template is only ever expanded by git archive.

Building pytest from a git checkout now requires setuptools-scm >= 10.1.
#9236: pluggy>=1.6 is now required.

Older pluggy versions stopped running the remaining hook wrapper teardowns once an
old-style hookwrapper raised in its own teardown. The logging plugin's wrapper was
left suspended, and when it was finalised later it detached the handler that
caplog of a subsequent test was recording through, so that test saw no records.

Contributor-facing changes

#14813: Added a systematic coverage matrix for assertion rewriting.
#14921: Added scripts/diff-assert-rewrite.py, which diffs the assert-rewritten form of a snippet between the plain source, this checkout and released pytest versions.
#15190: Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented DistFacade compatibility class.

Miscellaneous internal changes

#13888: FixtureRequest.node <pytest.FixtureRequest.node> is now explicitly annotated as returning Any, so strict pyright no longer reports it as Unknown. The return type stays deliberately broad, see 13888.
#14758: Internal node ids (the ::-separated strings identifying collected items, e.g. path/to/test_file.py::TestClass::test_method[param]) are now represented internally by a single structured ~_pytest.nodeid.NodeId dataclass instead of being repeatedly re-parsed as plain strings. The public nodeid: str attribute on nodes and reports is unchanged and remains fully backward compatible for plugins.

pytest 9.1.1 (2026-06-19)

Bug fixes

#14220: Fixed a logic bug in pytest.RaisesGroup which would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.
#14591: Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect @pytest.mark.parametrize to fail with "duplicate parametrization of '<fixture name>'".
#14606: Fixed list-item typing errors from mypy in @pytest.mark.parametrize <pytest.mark.parametrize ref> argvalues parameter.
#14608: Fixed a regression in pytest 9.1.0 where conftest.py files located in <invocation dir>/test* were no longer loaded as initial conftests when invoked without arguments.
This could cause certain hooks (like pytest_addoption) in these files to not fire.

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

#14533: When using --doctest-modules, autouse fixtures with module, package or session scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

If this is undesirable, move the fixture definition to a conftest.py file if possible.

Technical explanation for those interested:
When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration).
Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module.
This means that both need to register the fixtures independently.

Deprecations (removal in next major release)

#10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without @classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use @classmethod decorator instead -- by yastcher.

See 10819 and 14011.
#12882: Calling request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue> during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

See dynamic-fixture-request-during-teardown for details.
#13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.parametrize <pytest.Metafunc.parametrize> is now deprecated.

These iterables get exhausted after the first iteration,
leading to tests getting unexpectedly skipped in cases such as running pytest.main() multiple times,
using class-level parametrize decorators,
or collecting tests multiple times.

See parametrize-iterators for details and suggestions.
#13946: The private config.inicfg attribute is now deprecated.
Use config.getini() <pytest.Config.getini> to access configuration values instead.

See config-inicfg for more details.
#14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

Use the node parameter instead for fixture scoping. This enables more robust node-based
matching instead of string prefix matching.
If you've used nodeid=None, pass node=session instead.

This will be removed in pytest 10.
#14335: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10.
See hook-markers for more details.
#14434: The --pastebin option is now deprecated.
The same functionality is now available in an external plugin, pytest-pastebin.
See pastebin-deprecated for more details.
#14513: The private FixtureDef.has_location attribute is now deprecated and will be removed in pytest 10.
See fixturedef-has-location-deprecated for details.
#1764: pytest.console_main is now deprecated and will be removed in pytest 10.
It was never intended for programmatic use; use pytest.main instead.

New features

#12376: Added pytest.register_fixture() to register fixtures using an imperative interface.

This is an advanced function intended for use by plugins.

Normally, fixtures should be registered declaratively using the @pytest.fixture <pytest.fixture> decorator.
Pytest looks for these fixture definitions during the collection phase and registers them automatically.
For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used.
#14023: Added --report-chars long CLI option.
#14371: Added --max-warnings command-line option and max_warnings configuration option to fail the test run when the number of warnings exceeds a given threshold -- by miketheman.
#6757: Added the assertion_text_diff_style configuration option, allowing
string equality failures to be rendered as separate Left: and Right:
blocks instead of ndiff output.
#8395: Added support for ~datetime.datetime and ~datetime.timedelta comparisons with pytest.approx. An explicit abs or rel tolerance as a ~datetime.timedelta is required and relative tolerance is not supported for datetime comparisons -- by hamza-mobeen.

Improvements in existing functionality

#11225: pytest.warns now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the match pattern did not match.
#11295: Improved output of --fixtures-per-test by excluding internal-implementation fixtures generated by @pytest.mark.parametrize and similar.
#13241: pytest.raises, pytest.warns and pytest.deprecated_call now uses ParamSpec for the type hint to the (old and not recommended) callable overload, instead of Any. This allows type checkers to raise errors when passing incorrect function parameters.
func can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept.
#13862: Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr.
#14026: Added test coverage for compiled regex patterns in pytest.raises match parameter.
#14137: pytest.ScopeName is now public to allow using it in function signatures.
#14342: Marked yield_fixture as deprecated to type checkers using the deprecated decorator. Note it
has originally been deprecated <yield-fixture-deprecated> in pytest 6.2 already.
#14373: Added type annotations for pytest.approx.
#14430: When using --setup-show, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result.
#14441: Reduced the default number of gc.collect() passes in the unraisableexception plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via __del__. This can noticeably speed up test suites that trigger many pytester runs.
#14461: Improved assertion failure explanations for equality comparisons between mapping objects that are not dict instances.
#14513: The order in which fixture definitions overriding each other are resolved is now determined first by their visibility in the collection tree rather than by the order in which they are registered.

A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later.
Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins".
This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name.
#14524: Add official Python 3.15 support.
#1764: Improved argparse program name to show pytest, python -m pytest, or pytest.main() based on how pytest was invoked, making help and error messages clearer.
#8265: Emit a PytestCollectionWarning when a module-level __getattr__ returns None for pytestmark instead of raising AttributeError.

Previously this caused a cryptic TypeError: got None instead of Mark error.
Now pytest issues a helpful warning and continues collecting the module normally.

Bug fixes

#13192: Fixed | (pipe) not being treated as a regex meta-character that needs escaping in pytest.raises(match=...) <pytest.raises>.
#13484: Fixed -W option values being duplicated in Config.known_args_namespace.
#13626: Fixed function-scoped fixture values being kept alive after a test was interrupted by KeyboardInterrupt or early exit,
allowing them to potentially be released more promptly.
#13784: Fixed capteesys producing doubled output when used with --capture=no (-s).
#13817: Fixed a secondary AttributeError masking the original error when an option argument fails to initialize.
#13884: Fixed rare internal IndexError caused by builtins.compile being overridden in client code.
#13885: Fixed autouse fixtures defined inside a unittest.TestCase class running even when the class is decorated with unittest.skip or unittest.skipIf -- regression since pytest 8.1.0.
#13917: unittest.SkipTest is no longer considered an interactive exception, i.e. pytest_exception_interact is no longer called for it.
#13963: Fixed subtests running with pytest-xdist when their contexts contain objects that are not JSON-serializable.

Fixes pytest-dev/pytest-xdist#1273.
#14004: Fixed conftest.py fixture scoping when testpaths points outside of the rootdir <rootdir>.

Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
when using a relative testpaths like ../tests/sdk.

Conftest fixtures are now parsed during Directory <pytest.Directory> collection, using the Directory node for proper scoping.
#14050: Display dictionary differences in assertion failures using the original key insertion order instead of sorted order.
#14080: fix missing type annotations on Pytester.makepyfile and Pytester.maketxtfile methods.
#14114: An exception from pytest_fixture_post_finalizer no longer prevents fixtures from being torn down, causing additional errors in the following tests.
#14161: Fixed monkeypatch.setattr() <pytest.MonkeyPatch.setattr> leaving a stale entry on the undo stack when the underlying setattr() call fails (e.g. on immutable targets), causing an AttributeError crash during teardown.
#14214: Fixed -v hint in pytest.raises match diff not working because assertion verbosity was not propagated.
#14234: Allow pytest.HIDDEN_PARAM <hidden-param> in @pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref> typing.
#14248: Fixed direct parametrization causing the static fixture closure (as reflected in request.fixturenames <pytest.FixtureRequest.fixturenames>) to omit fixtures that are requested transitively from overridden fixtures.
#14263: Unraisable exceptions from finalizers are now collected during pytest_unconfigure, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active error filter could be removed before the exception surfaced and a late resource leak would pass silently. A -W error filter, or any filter matching pytest.PytestUnraisableExceptionWarning, now promotes these exceptions to failures regardless of plugin cleanup order.
#14377: Fixed crash in Config.get_terminal_writer when an assertion fails with the terminalreporter plugin disabled.
#14381: Fixed -V (short form of --version) to properly display the current version.
#14389: Improved pytest.raises(..., match=...) <pytest.raises> failures to suppress the mismatched exception as a cause of the resulting AssertionError.
#14392: Fixed a bug in pytest.raises(match=...) <pytest.raises> "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead.
#14442: Fixed a regression in pytest 9.0 where --strict-markers and --strict-config specified through addopts were silently ignored.

Note that when targeting pytest >= 9.0, it's nicer to use strict_markers and strict_config, or strict mode <strict mode>.
#14456: Fixed pytest.approx not recognizing types with __array_interface__ as numpy-like arrays.
#14474: Fixed a regression where -k and -m expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a SyntaxError about escaping.
#14483: Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by EternalRights
#14492: Fixed Code.getargs() incorrectly including local variable names in the returned argument tuple for functions with *args and/or **kwargs. The method was using co_flags bitmask values (4 and 8) directly as counts instead of converting them to 1 via bool(), and was not accounting for co_kwonlyargcount when var=True.
#3697: Logging capture now works for non-propagating loggers.
Previously only logs which reached the root logger were captured.
This includes caplog and the "Captured log calls" test reporting.
#3850: Fixed JUnit XML report: the tests attribute of the <testsuite> element now always matches the number of <testcase> elements in the file. In some cases (test passes but fails during teardown) the tests attribute would report an incorrect number of testcases in the XML file.
#5848: pytest_fixture_post_finalizer is no longer called extra times for the same fixture teardown in some cases.
#719: Fixed @pytest.mark.parametrize <pytest.mark.parametrize ref> not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., "arg,").

The trailing comma form now correctly behaves like the tuple form ("arg",), treating argvalues as a list of tuples to unpack.

Improved documentation

#11022: Document safer alternatives and scope guidance for monkeypatching standard library functions.
#11307: Document that @pytest.hookimpl(specname=...) only works for function names starting with pytest_.
#13038: Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures.
#13155: Clarified how the request fixture provides indirect parametrization values via request.param.
#13304: Clarified in the documentation that hook implementations defined in conftest.py files are not available to other plugins during their pytest_addoption() execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement pytest_addoption() to add their own command-line options.
#13902: Clarified how subtest progress markers are shown in the documentation.
#14012: The ini options ref section of the API Reference now specified the type and default value of every configuration option.
#14148: Documented a safe pytestconfig.cache access pattern when the
cacheprovider plugin is disabled.
#14303: The documentation is now built with Sphinx >= 9.
#14465: Updated the hooks how-to page to link the newhooks.py file in pytest-xdist at tag v3.8.0 instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on.

Miscellaneous internal changes

#14582: Improved the recursion traceback test to exercise all requested traceback styles.

pytest 9.0.3 (2026-04-07)

Bug fixes

#12444: Fixed pytest.approx which now correctly takes into account ~collections.abc.Mapping keys order to compare them.
#13634: 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: Fixed crash when a test raises an exceptiongroup with __tracebackhide__ = True.
#14195: Fixed an issue where non-string messages passed to unittest.TestCase.subTest() were not printed.
#14343: Fixed use of insecure temporary directory (CVE-2025-71176).

Improved documentation

#13388: Clarified documentation for -p vs PYTEST_PLUGINS plugin loading and fixed an incorrect -p example.
#13731: Clarified that capture fixtures (e.g. capsys and capfd) take precedence over the -s / --capture=no command-line options in Accessing captured output from a test function <accessing-captured-output>.
#14088: Clarified that the default pytest_collection hook sets session.items before it calls pytest_collection_finish, not after.
#14255: TOML integer log levels must be quoted: Updating reference documentation.

Contributor-facing changes

#12689: The test reports are now published to Codecov from GitHub Actions.
The test statistics is visible on the web interface.

-- by aleguy02

pytest 9.0.2 (2025-12-06)

Bug fixes

#13896: 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: Fixed the TOML type of the tmp_path_retention_count settings in the API reference from number to string.
#13946: 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: Fixed quadratic-time behavior when handling unittest subtests in Python 3.10.

Improved documentation

#4492: The API Reference now contains cross-reference-able documentation of pytest's command-line flags <command-line-flags>.

pytest 9.0.1 (2025-11-12)

Bug fixes

#13895: Restore support for skipping tests via raise unittest.SkipTest.
#13896: 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: Fixed the TOML type of the verbosity settings in the API reference from number to string.
#13910: 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: The tox configuration has been adjusted to make sure the desired
version string can be passed into its package_env through
the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
variable as a part of the release process -- by webknjaz.

Contributor-facing changes

#13891, #13942: The CI/CD part of the release automation is now capable of
creating GitHub Releases without having a Git checkout on
disk -- by bluetech and webknjaz.
#13933: The tox configuration has been adjusted to make sure the desired
version string can be passed into its package_env through
the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
variable as a part of the release process -- by webknjaz.

pytest 9.0.0 (2025-11-05)

New features

#1367: Support for subtests has been added.

subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

Example:
```
def contains_docstring(p: Path) -> bool:
 """Return True if the given Python file contains a top-level docstring."""
 ...

def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
 for path in Path.cwd().glob("*.py"):
 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, unittest.TestCase.subTest is now also supported.

This feature was originally implemented as a separate plugin in pytest-subtests, 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: 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 "INI compatibility mode", 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.
```
# pyproject.toml
[tool.pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]
```
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't use pyproject.toml, you can use pytest.toml or .pytest.toml:
```
# pytest.toml or .pytest.toml
[pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]
```
The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

See config file formats for full details.
#13823: Added a "strict mode" enabled by the strict configuration option.

When set to true, the strict option currently enables
- strict_config
- strict_markers
- strict_parametrization_ids
- strict_xfail
The individual strictness options can be explicitly set to override the global 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 strict mode for more details.
#13737: Added the 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: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence.
When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
you'll see the progress in the terminal tab or window,
allowing you to monitor pytest'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='-p no:terminalprogress'.
- On a project configuration level, using addopts = "-p no:terminalprogress".
#478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.

Previously, this option only impacted package imports, now it also impacts tests discovery.
#13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" 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 ogrisel.
#13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.

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: 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 sgaist
#13574: 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 PYTEST_ADDOPTS or addopts.
#13823: Added strict_xfail as an alias to the xfail_strict option,
strict_config as an alias to the --strict-config flag,
and strict_markers as an alias to the --strict-markers flag.
This makes all strictness options consistently have configuration options with the prefix strict_.
#13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.
#13732: 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: Clarify the error message for pytest.raises() when a regex match fails.
#13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".

Removals and backward incompatible breaking changes

#12083: 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 --keep-duplicates <duplicate-paths>, which retains its existing behavior (including the bug).
#13719: Support for Python 3.9 is dropped following its end of life.
#13766: 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.
#13779: 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
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:
```
[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 13779.

Deprecations (removal in next major release)

#13807: monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend> 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 (420).
See monkeypatch-fixup-namespace-packages for details.

Bug fixes

#13445: Made the type annotations of pytest.skip and friends more spec-complaint to have them work across more type checkers.
#13537: Fixed a bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.
#13598: Fixed possible collection confusion on Windows when short paths and symlinks are involved.
#13716: 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: Fixed a misleading assertion failure message when using pytest.approx on mappings with differing lengths.
#13773: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.
#13816: Fixed pytest.approx which now returns a clearer error message when comparing mappings with different keys.
#13849: 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: Fixed --show-capture with --tb=line.
#13522: Fixed pytester in subprocess mode ignored all :attr`pytester.plugins <pytest.Pytester.plugins>` except the first.

Fixed pytester in subprocess mode silently ignored non-str pytester.plugins <pytest.Pytester.plugins>.
Now it errors instead.
If you are affected by this, specify the plugin by name, or switch the affected tests to use pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess> explicitly instead.

Packaging updates and notes for downstreams

#13791: Minimum requirements on iniconfig and packaging were bumped to 1.0.1 and 22.0.0, respectively.

Contributor-facing changes

#12244: Fixed self-test failures when TERM=dumb.
#12474: Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.
#13621: pytest'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: Fixed deprecated gh pr new command in scripts/prepare-release-pr.py.
The script now uses gh pr create which is compatible with GitHub CLI v2.0+.
#13695: Flush stdout and stderr in Pytester.run to avoid truncated outputs in test_faulthandler.py::test_timeout on CI -- by ogrisel.
#13771: Skip test_do_not_collect_symlink_siblings on Windows environments without symlink support to avoid false negatives.
#13841: tox>=4 is now required when contributing to pytest.
#13625: Added missing docstrings to pytest_addoption(), pytest_configure(), and cacheshow() functions in cacheprovider.py.

Miscellaneous internal changes

#13830: Configuration overrides (-o/--override-ini) are now processed during startup rather than during config.getini() <pytest.Config.getini>.

pytest 8.4.2 (2025-09-03)

Bug fixes

#13478: Fixed a crash when using console_output_style{.interpreted-text role="confval"} with times and a module is skipped.
#13530: Fixed a crash when using pytest.approx{.interpreted-text role="func"} and decimal.Decimal{.interpreted-text role="class"} instances with the decimal.FloatOperation{.interpreted-text role="class"} trap set.
#13549: No longer evaluate type annotations in Python 3.14 when inspecting function signatures.

This prevents crashes during module collection when modules do not explicitly use from __future__ import annotations and import types for annotations within a if TYPE_CHECKING: block.
#13559: Added missing [int]{.title-ref} and [float]{.title-ref} variants to the [Literal]{.title-ref} type annotation of the [type]{.title-ref} parameter in pytest.Parser.addini{.interpreted-text role="meth"}.
#13563: pytest.approx{.interpreted-text role="func"} now only imports numpy if NumPy is already in sys.modules. This fixes unconditional import behavior introduced in [8.4.0]{.title-ref}.

Improved documentation

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

Contributor-facing changes

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

pytest 8.4.1 (2025-06-17)

Bug fixes

#13461: Corrected _pytest.terminal.TerminalReporter.isatty to support
being called as a method. Before it was just a boolean which could
break correct code when using -o log_cli=true).
#13477: Reintroduced pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.

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

See return-not-none{.interpreted-text role="ref"} for more information.
#13497: Fixed compatibility with Twisted 25+.

Improved documentation

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

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

#11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.
#12346: Tests will now fail, instead of raising a warning, if they return any value other than None.
#12874: We dropped support for Python 3.8 following its end of life (2024-10-07).
#12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

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

Deprecations (removal in next major release)

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

New features

#11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.
#12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.
#12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.
#12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.
#12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

For example:
```
# contents of src/domain.py
class Testament: ...

# contents of tests/test_testament.py
from domain import Testament

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

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

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

See truncation-params{.interpreted-text role="ref"} for more information.
#13125: console_output_style{.interpreted-text role="confval"} now supports times to show execution time of each test.
#13192: pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string to match, as this will match against any value. Use match="^$" if you want to check that an exception has no message.
#13192: pytest.raises{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has ^ and $ and is otherwise escaped.
#13192: You can now pass with pytest.raises(check=fn): <pytest.raises>{.interpreted-text role="func"}, where fn is a function which takes a raised exception and returns a boolean. The raises fails if no exception was raised (as usual), passes if an exception is raised and fn returns True (as well as match and the type matching, if specified, which are checked before), and propagates the exception if fn returns False (which likely also fails the test).
#13228: hidden-param{.interpreted-text role="ref"} can now be used in id of pytest.param{.interpreted-text role="func"} or in
ids of Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"}.
It hides the parameter set from the test name.
#13253: New flag: --disable-plugin-autoload <disable_plugin_autoload>{.interpreted-text role="ref"} which works as an alternative to PYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files with addopts{.interpreted-text role="confval"}.

Improvements in existing functionality

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

================================= FAILURES =================================
_______________________ test_gets_correct_tracebacks _______________________

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

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

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

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

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

Example:

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

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

[pytest]
int_value = 3
float_value = 5.4

#11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.

-- by the-compiler{.interpreted-text role="user"} and glyphack{.interpreted-text role="user"}
#12426: A warning is now issued when pytest.mark.usefixtures ref{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.
#12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.
#12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.

This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.
#12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.
#12958: A number of unraisable <unraisable>{.interpreted-text role="ref"} enhancements:
- Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions.
- Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions.
- Collect multiple unraisable exceptions per test phase.
- Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
- Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
- Report the unraisable exception as the cause of the pytest.PytestUnraisableExceptionWarning{.interpreted-text role="class"} exception if raised.
- Compute the repr of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.
#13010: pytest.approx{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.
#13016: A number of threadexception <unraisable>{.interpreted-text role="ref"} enhancements:
- Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads.
- Collect multiple thread exceptions per test phase.
- Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
- Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
- Report the thread exception as the cause of the pytest.PytestUnhandledThreadExceptionWarning{.interpreted-text role="class"} exception if raised.
- Extract the name of the thread object in the excepthook which should help with resurrection of the thread.
#13031: An empty parameter set as in pytest.mark.parametrize([], ids=idfunc) will no longer trigger a call to idfunc with internal objects.
#13115: Allows supplying ExceptionGroup[Exception] and BaseExceptionGroup[BaseException] to pytest.raises to keep full typing on ExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"}:
```
with pytest.raises(ExceptionGroup[Exception]) as exc_info:
 some_function()
```
Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.
#13122: The --stepwise mode received a number of improvements:
- It no longer forgets the last failed test in case pytest is executed later without the flag.
  
  This enables the following workflow:
  1. Execute pytest with --stepwise, pytest then stops at the first failing test;
  2. Iteratively update the code and run the test in isolation, without the --stepwise flag (for example in an IDE), until it is fixed.
  3. Execute pytest with --stepwise again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.
  Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.
  
  This change however might cause issues if the --stepwise mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).
- New --stepwise-reset/--sw-reset flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.
#13308: Added official support for Python 3.14.
#13380: Fix ExceptionGroup{.interpreted-text role="class"} traceback filtering to exclude pytest internals.
#13415: The author metadata of the BibTex example is now correctly formatted with last names following first names.
An example of BibLaTex has been added.
BibTex and BibLaTex examples now clearly indicate that what is cited is software.

-- by willynilly{.interpreted-text role="user"}
#13420: Improved test collection performance by optimizing path resolution used in FSCollector.
#13457: The error message about duplicate parametrization no longer displays an internal stack trace.
#4112: Using pytest.mark.usefixtures <pytest.mark.usefixtures ref>{.interpreted-text role="ref"} on pytest.param{.interpreted-text role="func"} now produces an error instead of silently doing nothing.
#5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling pytest.main{.interpreted-text role="func"}.

[#&#8203;6985](https://github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.

:   -   The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.

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

        Example:

        **Previous Output:**

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

        **Current Output:**

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

    \-- by `fazeelghafoor`{.interpreted-text role="user"}

#7683: The formerly optional pygments dependency is now required, causing output always to be source-highlighted (unless disabled via the --code-highlight=no CLI option).

Bug fixes

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

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

This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered.
#11067: The test report is now consistent regardless if the test xfailed via pytest.mark.xfail <pytest.mark.xfail ref>{.interpreted-text role="ref"} or pytest.fail{.interpreted-text role="func"}.

Previously, xfailed tests via the marker would have the string "reason: " prefixed to the message, while those xfailed via the function did not. The prefix has been removed.
#12008: In 11220{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted.
#12863: Fix applying markers, including pytest.mark.parametrize <pytest.mark.parametrize ref>{.interpreted-text role="ref"} when placed above [@staticmethod]{.title-ref} or [@classmethod]{.title-ref}.
#12929: Handle StopIteration from test cases, setup and teardown correctly.
#12938: Fixed --durations-min argument not respected if -vv is used.
#12946: Fixed missing help for pdb{.interpreted-text role="mod"} commands wrapped by pytest -- by adamchainz{.interpreted-text role="user"}.
#12981: Prevent exceptions in pytest.Config.add_cleanup{.interpreted-text role="func"} callbacks preventing further cleanups.
#13047: Restore pytest.approx{.interpreted-text role="func"} handling of equality checks between [bool]{.title-ref} and [numpy.bool_]{.title-ref} types.

Comparing [bool]{.title-ref} and [numpy.bool_]{.title-ref} using pytest.approx{.interpreted-text role="func"} accidentally changed in version [8.3.4]{.title-ref} and [8.3.5]{.title-ref} to no longer match:
```
>>> import numpy as np
>>> from pytest import approx
>>> [np.True_, np.True_] == pytest.approx([True, True])
False
```
This has now been fixed:
```
>>> [np.True_, np.True_] == pytest.approx([True, True])
True
```
#13119: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.
#13175: The diff is now also highlighted correctly when comparing two strings.
#13248: Fixed an issue where passing a scope in Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"} with indirect=True
could result in other fixtures being unable to depend on the parametrized fixture.
#13291: Fixed repr of attrs objects in assertion failure messages when using attrs>=25.2.
#13312: Fixed a possible KeyError crash on PyPy during collection of tests involving higher-scoped parameters.
#13345: Fix type hints for pytest.TestReport.when{.interpreted-text role="attr"} and pytest.TestReport.location{.interpreted-text role="attr"}.
#13377: Fixed handling of test methods with positional-only parameter syntax.

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

    def test_method(self, /, *, fixture): ...
```
Before, this caused an internal error in pytest.
#13384: Fixed an issue where pytest could report negative durations.
#13420: Added lru_cache to nodes._check_initialpaths_for_relpath.
#9037: Honor disable_test_id_escaping_and_forfeit_all_rights_to_community_support{.interpreted-text role="confval"} when escaping ids in parametrized tests.

Improved documentation

#12535: [This
example]{.title-ref}<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures>
showed print statements that do not exactly reflect what the
different branches actually do. The fix makes the example more precise.
#13218: Pointed out in the pytest.approx{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one.
#13221: Improved grouping of CLI options in the --help output.
#6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the api-reference{.interpreted-text role="ref"} documentation page.
#8612: Add a recipe for handling abstract test classes in the documentation.

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

Packaging updates and notes for downstreams

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

Contributor-facing changes

#12017: Mixed internal improvements:
- Migrate formatting to f-strings in some tests.
- Use type-safe constructs in JUnitXML tests.
- MovedMockTiming into _pytest.timing.
-- by RonnyPfannschmidt{.interpreted-text role="user"}
#12647: Fixed running the test suite with the hypothesis pytest plugin.

Miscellaneous internal changes

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

`v8.3.5`

Compare Source

pytest 8.3.5 (2025-03-02)

Bug fixes

#11777: Fixed issue where sequences were still being shortened even with -vv verbosity.
#12888: 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: Fixed AttributeError{.interpreted-text role="class"} crash when using --import-mode=importlib when top-level directory same name as another module of the standard library.
#13053: 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: Fixed issue where pytest could crash if one of the collected directories got removed during collection.

Improved documentation

#12842: Added dedicated page about using types with pytest.

See types{.interpreted-text role="ref"} for detailed usage.

Contributor-facing changes

#13112: Fixed selftest failures in test_terminal.py with Pygments >= 2.19.0
#13256: Support for Towncrier versions released in 2024 has been re-enabled
when building Sphinx docs -- by webknjaz{.interpreted-text role="user"}.

`v8.3.4`

Compare Source

pytest 8.3.4 (2024-12-01)

Bug fixes

#12592: Fixed KeyError{.interpreted-text role="class"} crash when using --import-mode=importlib in a directory layout where a directory contains a child directory with the same name.
#12818: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the AST, like executing.
#12849: ANSI escape codes for colored output now handled correctly in pytest.fail{.interpreted-text role="func"} with [pytrace=False]{.title-ref}.
#9353: pytest.approx{.interpreted-text role="func"} now uses strict equality when given booleans.

Improved documentation

#10558: Fix ambiguous docstring of pytest.Config.getoption{.interpreted-text role="func"}.
#10829: Improve documentation on the current handling of the --basetemp option and its lack of retention functionality (temporary directory location and retention{.interpreted-text role="ref"}).
#12866: Improved cross-references concerning the recwarn{.interpreted-text role="fixture"} fixture.
#12966: Clarify filterwarnings{.interpreted-text role="ref"} docs on filter precedence/order when using multiple @pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>{.interpreted-text role="ref"} marks.

Contributor-facing changes

#12497: Fixed two failing pdb-related tests on Python 3.13.

`v8.3.3`

Compare Source

pytest 8.3.3 (2024-09-09)

Bug fixes

#12446: Avoid calling @property (and other instance descriptors) during fixture discovery -- by asottile{.interpreted-text role="user"}
#12659: Fixed the issue of not displaying assertion failure differences when using the parameter --import-mode=importlib in pytest>=8.1.
#12667: Fixed a regression where type change in [ExceptionInfo.errisinstance]{.title-ref} caused [mypy]{.title-ref} to fail.
#12744: Fixed typing compatibility with Python 3.9 or less -- replaced [typing.Self]{.title-ref} with [typing_extensions.Self]{.title-ref} -- by Avasam{.interpreted-text role="user"}
#12745: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.
#6682: Fixed bug where the verbosity levels where not being respected when printing the "msg" part of failed assertion (as in assert condition, msg).
#9422: Fix bug where disabling the terminal plugin via -p no:terminal would cause crashes related to missing the verbose option.

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

Improved documentation

#12663: Clarify that the [pytest_deselected]{.title-ref} hook should be called from [pytest_collection_modifyitems]{.title-ref} hook implementations when items are deselected.
#12678: Remove erroneous quotes from [tmp_path_retention_policy]{.title-ref} example in docs.

Miscellaneous internal changes

#12769: Fix typos discovered by codespell and add codespell to pre-commit hooks.

`v8.3.2`

Compare Source

pytest 8.3.2 (2024-07-24)

Bug fixes

#12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.

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

`v8.3.1`

Compare Source

pytest 8.3.1 (2024-07-20)

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.

`v8.3.0`

Compare Source

pytest 8.3.0 (2024-07-20)

New features

#12231: Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.
- If the [--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown.
- The style of traceback for XFAIL is set with [--tb]{.title-ref}, and can be [auto|long|short|line|native|no]{.title-ref}.
- Note: Even if you have [--xfail-tb]{.title-ref} set, you won't see them if [--tb=no]{.title-ref}.
Some history:

With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} 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't want to see all of the xfail tracebacks.

This change detaches xfail tracebacks from [-rx]{.title-ref}, and now we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this, the default [-rx]{.title-ref}/ [-ra]{.title-ref} 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.
#12281: Added support for keyword matching in marker expressions.

Now tests can be selected by marker keyword arguments.
Supported values are int{.interpreted-text role="class"}, (unescaped) str{.interpreted-text role="class"}, bool{.interpreted-text role="class"} & None{.interpreted-text role="data"}.

See marker examples <marker_keyword_expression_example>{.interpreted-text role="ref"} for more information.

-- by lovetheguitar{.interpreted-text role="user"}
#12567: 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 pbrezina{.interpreted-text role="user"}

Improvements in existing functionality

#12469: The console output now uses the "third-party plugins" terminology,
replacing the previously established but confusing and outdated
reference to setuptools <setuptools:index>{.interpreted-text role="std:doc"}
-- by webknjaz{.interpreted-text role="user"}.
#12544, #12545: Python virtual environment detection was improved by
checking for a pyvenv.cfg{.interpreted-text role="file"} file, ensuring reliable detection on
various platforms -- by zachsnickers{.interpreted-text role="user"}.
#2871: Do not truncate arguments to functions in output when running with [-vvv]{.title-ref}.

#389: The readability of assertion introspection of bound methods has been enhanced
-- by farbodahm{.interpreted-text role="user"}, webknjaz{.interpreted-text role="user"}, obestwalter{.interpreted-text role="user"}, flub{.interpreted-text role="user"}
and glyphack{.interpreted-text role="user"}.

Earlier, it was like:

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

    def test():
>       assert Help().fun() == 2
E       assert 1 == 2
E        +  where 1 = <bound method Help.fun of <example.Help instance at 0x256a830>>()
E        +    where <bound method Help.fun of <example.Help instance at 0x256a830>> = <example.Help instance at 0x256a830>.fun
E        +      where <example.Help instance at 0x256a830> = Help()

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

And now it's like:

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

    def test():
>       assert Help().fun() == 2
E       assert 1 == 2
E        +  where 1 = fun()
E        +    where fun = <test_local.Help object at 0x1074be230>.fun
E        +      where <test_local.Help object at 0x1074be230> = Help()

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

#7662: Added timezone information to the testsuite timestamp in the JUnit XML report.

Bug fixes

#11706: Fixed reporting of teardown errors in higher-scoped fixtures when using [--maxfail]{.title-ref} or [--stepwise]{.title-ref}.

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: pytest.approx{.interpreted-text role="func"} now correctly handles Sequence <collections.abc.Sequence>{.interpreted-text role="class"}-like objects.
#12204, #12264: 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 bluetech{.interpreted-text role="user"}.

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: Fixed collection error upon encountering an abstract <abc>{.interpreted-text role="mod"} class, including abstract [unittest.TestCase]{.title-ref} subclasses.
#12328: 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: Fixed crash with [assert testcase is not None]{.title-ref} assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2.
#12472: Fixed a crash when returning category "error" or "failed" with a custom test status from pytest_report_teststatus{.interpreted-text role="hook"} hook -- pbrezina{.interpreted-text role="user"}.
#12505: Improved handling of invalid regex patterns in pytest.raises(match=r'...') <pytest.raises>{.interpreted-text role="func"} by providing a clear error message.
#12580: Fixed a crash when using the cache class on Windows and the cache directory was created concurrently.
#6962: Parametrization parameters are now compared using [==]{.title-ref} instead of [is]{.title-ref} ([is]{.title-ref} is still used as a fallback if the parameter does not support [==]{.title-ref}).
This fixes use of parameters such as lists, which have a different [id]{.title-ref} but compare equal, causing fixtures to be re-computed instead of being cached.
#7166: Fixed progress percentages (the [ 87%] at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist -n.

Improved documentation

#12153: Documented using PYTEST_VERSION{.interpreted-text role="envvar"} to detect if code is running from within a pytest run.
#12469: The external plugin mentions in the documentation now avoid mentioning
setuptools entry-points <setuptools:index>{.interpreted-text role="std:doc"} as the concept is
much more generic nowadays. Instead, the terminology of "external",
"installed", or "third-party" plugins (or packages) replaces that.

-- by webknjaz{.interpreted-text role="user"}
#12577: [CI]{.title-ref} and [BUILD_NUMBER]{.title-ref} environment variables role is discribed in
the reference doc. They now also appear when doing [pytest -h]{.title-ref}
-- by MarcBresson{.interpreted-text role="user"}.

Contributor-facing changes

#12467: Migrated all internal type-annotations to the python3.10+ style by using the [annotations]{.title-ref} future import.

-- by RonnyPfannschmidt{.interpreted-text role="user"}
#11771, #12557: 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 x612skm{.interpreted-text role="user"}
#12493: 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
doc/en/_changelog_towncrier_draft.rst{.interpreted-text role="file"}. 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:
```
$ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst
```
-- by webknjaz{.interpreted-text role="user"}
#12498: All the undocumented tox environments now have descriptions.
They can be listed in one's development environment by invoking
tox -av in a terminal.

-- by webknjaz{.interpreted-text role="user"}
#12501: 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 webknjaz{.interpreted-text role="user"}
#12502: The UX of the GitHub automation making pull requests to update the
plugin list has been updated. Previously, the maintainers had to close
the automatically created pull requests and re-open them to trigger the
CI runs. From now on, they only need to click the [Ready for review]{.title-ref}
button instead.

-- by webknjaz{.interpreted-text role="user"}
#12522: The :pull: RST role has been replaced with a shorter
:pr: due to starting to use the implementation from
the third-party sphinx-issues{.interpreted-text role="pypi"} Sphinx extension
-- by webknjaz{.interpreted-text role="user"}.
#12531: The coverage reporting configuration has been updated to exclude
pytest's own tests marked as expected to fail from the coverage
report. This has an effect of reducing the influence of flaky
tests on the resulting number.

-- by webknjaz{.interpreted-text role="user"}
#12533: The extlinks Sphinx extension is no longer enabled. The :bpo:
role it used to declare has been removed with that. BPO itself has
migrated to GitHub some years ago and it is possible to link the
respective issues by using their GitHub issue numbers and the
:issue: role that the sphinx-issues extension implements.

-- by webknjaz{.interpreted-text role="user"}
#12562: Possible typos in using the :user: RST role is now being linted
through the pre-commit tool integration -- by webknjaz{.interpreted-text role="user"}.

`v8.2.2`

Compare Source

pytest 8.2.2 (2024-06-04)

Bug Fixes

#12355: Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.
#12367: Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.
#12381: Fix possible "Directory not empty" crashes arising from concurent cache dir (.pytest_cache) creation. Regressed in pytest 8.2.0.

Improved Documentation

#12290: Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.
#12356: Added a subsection to the documentation for debugging flaky tests to mention
lack of thread safety in pytest as a possible source of flakyness.
#12363: The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.

`v8.2.1`

Compare Source

pytest 8.2.1 (2024-05-19)

Improvements

#12334: Support for Python 3.13 (beta1 at the time of writing).

Bug Fixes

#12120: Fix [PermissionError]{.title-ref} crashes arising from directories which are not selected on the command-line.
#12191: Keyboard interrupts and system exits are now properly handled during the test collection.
#12300: Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only.
#12308: Fix a regression in pytest 8.2.0 where the permissions of automatically-created .pytest_cache directories became rwx------ instead of the expected rwxr-xr-x.

Trivial/Internal Changes

#12333: pytest releases are now attested using the recent Artifact Attestation support from GitHub, allowing users to verify the provenance of pytest's sdist and wheel artifacts.

`v8.2.0`

Compare Source

pytest 8.2.0 (2024-04-27)

Deprecations

#12069: A deprecation warning is now raised when implementations of one of the following hooks request a deprecated py.path.local parameter instead of the pathlib.Path parameter which replaced it:
- pytest_ignore_collect{.interpreted-text role="hook"} - the path parameter - use collection_path instead.
- pytest_collect_file{.interpreted-text role="hook"} - the path parameter - use file_path instead.
- pytest_pycollect_makemodule{.interpreted-text role="hook"} - the path parameter - use module_path instead.
- pytest_report_header{.interpreted-text role="hook"} - the startdir parameter - use start_path instead.
- pytest_report_collectionfinish{.interpreted-text role="hook"} - the startdir parameter - use start_path instead.
The replacement parameters are available since pytest 7.0.0.
The old parameters will be removed in pytest 9.0.0.

See legacy-path-hooks-deprecated{.interpreted-text role="ref"} for more details.

Features

#11871: Added support for reading command line arguments from a file using the prefix character @, like e.g.: pytest @tests.txt. The file must have one argument per line.

See Read arguments from file <args-from-file>{.interpreted-text role="ref"} for details.

Improvements

#11523: pytest.importorskip{.interpreted-text role="func"} will now issue a warning if the module could be found, but raised ImportError{.interpreted-text role="class"} instead of ModuleNotFoundError{.interpreted-text role="class"}.

The warning can be suppressed by passing exc_type=ImportError to pytest.importorskip{.interpreted-text role="func"}.

See import-or-skip-import-error{.interpreted-text role="ref"} for details.
#11728: For unittest-based tests, exceptions during class cleanup (as raised by functions registered with TestCase.addClassCleanup <unittest.TestCase.addClassCleanup>{.interpreted-text role="meth"}) are now reported instead of silently failing.
#11777: Text is no longer truncated in the short test summary info section when -vv is given.
#12112: Improved namespace packages detection when consider_namespace_packages{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs).
#9502: Added PYTEST_VERSION{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value of pytest.__version__, and among other things can be used to easily check if code is running from within a pytest run.

Bug Fixes

#12065: Fixed a regression in pytest 8.0.0 where test classes containing setup_method and tests using @staticmethod or @classmethod would crash with AttributeError: 'NoneType' object has no attribute 'setup_method'.

Now the request.instance <pytest.FixtureRequest.instance>{.interpreted-text role="attr"} attribute of tests using @staticmethod and @classmethod is no longer None, but a fresh instance of the class, like in non-static methods.
Previously it was None, and all fixtures of such tests would share a single self.
#12135: Fixed issue where fixtures adding their finalizer multiple times to fixtures they request would cause unreliable and non-intuitive teardown ordering in some instances.
#12194: Fixed a bug with --importmode=importlib and --doctest-modules where child modules did not appear as attributes in parent modules.
#1489: Fixed some instances where teardown of higher-scoped fixtures was not happening in the reverse order they were initialized in.

Trivial/Internal Changes

#12069: pluggy>=1.5.0 is now required.
#12167: cache <cache>{.interpreted-text role="ref"}: create supporting files (CACHEDIR.TAG, .gitignore, etc.) in a temporary directory to provide atomic semantics.

`v8.1.2`

Compare Source

pytest 8.1.2 (2024-04-26)

Bug Fixes

#12114: Fixed error in pytest.approx{.interpreted-text role="func"} when used with [numpy]{.title-ref} arrays and comparing with other types.

`v8.1.1`

Compare Source

pytest 8.1.1 (2024-03-08)

::: {.note}
::: {.title}
Note
:::

This release is not a usual bug fix release -- it contains features and improvements, being a follow up
to 8.1.0, which has been yanked from PyPI.
:::

Features

#11475: Added the new consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting to False.

If set to True, pytest will attempt to identify modules that are part of namespace packages when importing modules.
#11653: Added the new verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.
See Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.

Improvements

#10865: pytest.warns{.interpreted-text role="func"} now validates that warnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.
Currently in Python it is possible to use other types, however this causes an exception when warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see CPython #103577 for a discussion).
While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using --override-ini for paths in invocations without a configuration file defined, the current working directory is used
as the relative directory.

Previoulsy this would raise an AssertionError{.interpreted-text role="class"}.
#11475: --import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.

This means that installed packages will be imported under their canonical name if possible first, for example app.core.models, instead of having the module name always be derived from their path (for example .env310.lib.site_packages.app.core.models).
#11801: Added the iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes.
It is similar to listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.
#11850: Added support for sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.
#11962: In case no other suitable candidates for configuration file are found, a pyproject.toml (even without a [tool.pytest.ini_options] table) will be considered as the configuration file and define the rootdir.
#11978: Add --log-file-mode option to the logging plugin, enabling appending to log-files. This option accepts either "w" or "a" and defaults to "w".

Previously, the mode was hard-coded to be "w" which truncates the file before logging.
#12047: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group.
Previously, only the first exception was reported.

Bug Fixes

#11475: Fixed regression where --importmode=importlib would import non-test modules more than once.
#11904: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using --pyargs.

This change improves the collection tree for tests specified using --pyargs, see 12043{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.
#12011: Fixed a regression in 8.0.1 whereby setup_module xunit-style fixtures are not executed when --doctest-modules is passed.
#12014: Fix the stacklevel used when warning about marks used on fixtures.
#12039: Fixed a regression in 8.0.2 where tests created using tmp_path{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.

Improved Documentation

#11790: Documented the retention of temporary directories created using the tmp_path fixture in more detail.

Trivial/Internal Changes

#11785: Some changes were made to private functions which may affect plugins which access them:
- FixtureManager._getautousenames() now takes a Node itself instead of the nodeid.
- FixtureManager.getfixturedefs() now takes the Node itself instead of the nodeid.
- The _pytest.nodes.iterparentnodeids() function is removed without replacement.
  Prefer to traverse the node hierarchy itself instead.
  If you really need to, copy the function from the previous pytest release.
#12069: Delayed the deprecation of the following features to 9.0.0:
- node-ctor-fspath-deprecation{.interpreted-text role="ref"}.
- legacy-path-hooks-deprecated{.interpreted-text role="ref"}.
It was discovered after 8.1.0 was released that the warnings about the impeding removal were not being displayed, so the team decided to revert the removal.

This is the reason for 8.1.0 being yanked.

pytest 8.1.0 (YANKED)

::: {.note}
::: {.title}
Note
:::

This release has been yanked: it broke some plugins without the proper warning period, due to
some warnings not showing up as expected.

See #12069.
:::

`v8.1.0`

Compare Source

pytest 8.1.0 (YANKED)

[!IMPORTANT]
This release has been yanked: it broke some plugins without the proper warning period, due to some warnings not showing up as expected. See #12069.

Features

#11475: Added the new consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting to False.

If set to True, pytest will attempt to identify modules that are part of namespace packages when importing modules.
#11653: Added the new verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.
See Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.

Improvements

#10865: pytest.warns{.interpreted-text role="func"} now validates that warnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.
Currently in Python it is possible to use other types, however this causes an exception when warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see CPython #103577 for a discussion).
While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using --override-ini for paths in invocations without a configuration file defined, the current working directory is used
as the relative directory.

Previoulsy this would raise an AssertionError{.interpreted-text role="class"}.
#11475: --import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.

This means that installed packages will be imported under their canonical name if possible first, for example app.core.models, instead of having the module name always be derived from their path (for example .env310.lib.site_packages.app.core.models).
#11801: Added the iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes.
It is similar to listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.
#11850: Added support for sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.
#11962: In case no other suitable candidates for configuration file are found, a pyproject.toml (even without a [tool.pytest.ini_options] table) will be considered as the configuration file and define the rootdir.
#11978: Add --log-file-mode option to the logging plugin, enabling appending to log-files. This option accepts either "w" or "a" and defaults to "w".

Previously, the mode was hard-coded to be "w" which truncates the file before logging.
#12047: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group.
Previously, only the first exception was reported.

Bug Fixes

#11904: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using --pyargs.

This change improves the collection tree for tests specified using --pyargs, see 12043{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.
#12011: Fixed a regression in 8.0.1 whereby setup_module xunit-style fixtures are not executed when --doctest-modules is passed.
#12014: Fix the stacklevel used when warning about marks used on fixtures.
#12039: Fixed a regression in 8.0.2 where tests created using tmp_path{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.

Improved Documentation

#11790: Documented the retention of temporary directories created using the tmp_path fixture in more detail.

Trivial/Internal Changes

#11785: Some changes were made to private functions which may affect plugins which access them:
- FixtureManager._getautousenames() now takes a Node itself instead of the nodeid.
- FixtureManager.getfixturedefs() now takes the Node itself instead of the nodeid.
- The _pytest.nodes.iterparentnodeids() function is removed without replacement.
  Prefer to traverse the node hierarchy itself instead.
  If you really need to, copy the function from the previous pytest release.

`v8.0.2`

Compare Source

pytest 8.0.2 (2024-02-24)

Bug Fixes

#11895: Fix collection on Windows where initial paths contain the short version of a path (for example c:\PROGRA~1\tests).
#11953: Fix an IndexError crash raising from getstatementrange_ast.
#12021: Reverted a fix to [--maxfail]{.title-ref} handling in pytest 8.0.0 because it caused a regression in pytest-xdist whereby session fixture teardowns may get executed multiple times when the max-fails is reached.

`v8.0.1`

Compare Source

pytest 8.0.1 (2024-02-16)

Bug Fixes

#11875: Correctly handle errors from getpass.getuser{.interpreted-text role="func"} in Python 3.13.
#11879: Fix an edge case where ExceptionInfo._stringify_exception could crash pytest.raises{.interpreted-text role="func"}.
#11906: Fix regression with pytest.warns{.interpreted-text role="func"} using custom warning subclasses which have more than one parameter in their [__init__]{.title-ref}.
#11907: Fix a regression in pytest 8.0.0 whereby calling pytest.skip{.interpreted-text role="func"} and similar control-flow exceptions within a pytest.warns(){.interpreted-text role="func"} block would get suppressed instead of propagating.
#11929: Fix a regression in pytest 8.0.0 whereby autouse fixtures defined in a module get ignored by the doctests in the module.
#11937: Fix a regression in pytest 8.0.0 whereby items would be collected in reverse order in some circumstances.

`v8.0.0`: pytest 8.0.0 (2024-01-27)

Compare Source

See 8.0.0rc1 and 8.0.0rc2 for the full changes since pytest 7.4!

Bug Fixes

#11842: Properly escape the reason of a skip <pytest.mark.skip ref>{.interpreted-text role="ref"} mark when writing JUnit XML files.
#11861: Avoid microsecond exceeds 1_000_000 when using log-date-format with %f specifier, which might cause the test suite to crash.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [pytest](https://github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | major | `==7.4.4` → `==9.2.0` | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.2.0`](https://github.com/pytest-dev/pytest/releases/tag/9.2.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/9.1.1...9.2.0) ### pytest 9.2.0 (2026-10-27) #### Removals and backward incompatible breaking changes - [#14716](https://github.com/pytest-dev/pytest/issues/14716): `-c` now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled `FileNotFoundError`. - [#8593](https://github.com/pytest-dev/pytest/issues/8593): The `indirect`, `ids` and `scope` arguments of `Metafunc.parametrize() <pytest.Metafunc.parametrize>` -- and therefore of `@pytest.mark.parametrize <pytest.mark.parametrize ref>` -- are now keyword-only. Passing them positionally was a common source of confusing errors, e.g. `parametrize("arg1", "arg2", [(1, 2)])` made the argvalues land in `indirect` and failed with `indirect fixture '(1, 2)' doesn't exist`; such mistakes now fail with an understandable `TypeError`. The type annotations have always declared these arguments as keyword-only. - [#993](https://github.com/pytest-dev/pytest/issues/993): Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code `1`: - a plugin that cannot be found -- via `-p`, `pytest_plugins` or `PYTEST_PLUGINS` -- exits with `pytest.ExitCode` `USAGE_ERROR` (`4`), like a `conftest.py` that fails to import; - a plugin that is found but raises while importing -- including a broken `pytest11` entry point or a missing plugin dependency -- exits with `pytest.ExitCode` `INTERNAL_ERROR` (`3`), with the traceback preserved. `pytest.main` now returns these codes instead of raising `ImportError`. Also fixed an `IndexError` from pytest's own internals when the plugin raised an exception with no arguments. #### Deprecations (removal in next major release) - [#14742](https://github.com/pytest-dev/pytest/issues/14742): The private `_pytest.python.CallSpec2` name has been renamed to `CallSpec`. The old `CallSpec2` alias remains available for now and will be removed in pytest 10 or 11. - [#14755](https://github.com/pytest-dev/pytest/issues/14755): Schedule *yield_fixture* decorator for removal in pytest 10 or 11. - [#14774](https://github.com/pytest-dev/pytest/issues/14774): Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1, *all* higher-scoped fixtures (`module`, `package`, and `session`) defined as instance methods are now deprecated. They suffer from the same issue the original deprecation only fixed for class-scoped fixtures, see `10819` and `14011`. - [#14808](https://github.com/pytest-dev/pytest/issues/14808): Passing a non-string value to a `string`-typed ini option now emits a `pytest.PytestRemovedIn10Warning`. This affects `[tool.pytest.ini_options]` in `pyproject.toml`. In pytest 10 this will raise a `TypeError`, matching the behavior of the corresponding TOML config path. - [#7323](https://github.com/pytest-dev/pytest/issues/7323): Passing `bytes` to `TerminalReporter.write_line()` is now deprecated, pass a `str` instead. #### New features - [#14743](https://github.com/pytest-dev/pytest/issues/14743): Full diff: now contains a legend explaining the + & - symbols in diff output. - [#2781](https://github.com/pytest-dev/pytest/issues/2781): When `strict_markers` is enabled, marker names used in `-m` expressions are now validated against registered markers. - [#6881](https://github.com/pytest-dev/pytest/issues/6881): Added the `parametrize_long_str_id_strategy` configuration option to control how long `str`/`bytes` parameter values are handled in auto-generated test IDs. Explicit IDs set via `ids=[...]` or `pytest.param(..., id=...)` are not affected. Available strategies: `short` (default, values over 100 chars fall back to `argname+index`), `sha256` (SHA-256 hex digest), `legacy` (keep full value), and `disallow` (error requesting explicit IDs). #### Improvements in existing functionality - [#10745](https://github.com/pytest-dev/pytest/issues/10745): A `RecursionError` whose recursion origin cannot be located now shows only the first and last 10 stack frames, matching what pytest already did when locating the origin failed outright. Previously the full traceback -- often around a thousand near-identical frames -- was rendered, which was both slow and unreadable. Pass `--full-trace` to see every frame. - [#10745](https://github.com/pytest-dev/pytest/issues/10745): The line numbers of a module's statements are now computed once per traceback instead of once per traceback entry, which noticeably speeds up rendering failures raised from large test modules. - [#11418](https://github.com/pytest-dev/pytest/issues/11418): The cached rewritten modules in `__pycache__` are now invalidated by a hash of the source instead of its modification time, using the checked-hash pyc format from `552`. Timestamps make the cache useless wherever source files get fresh modification times, most notably in CI: a checkout gives every file a new mtime, so a restored cache is discarded in full and every test module is rewritten again. Hashing the source costs roughly 15 microseconds per file and makes the cache survive that. Existing timestamp based caches are ignored and rewritten once. - [#12624](https://github.com/pytest-dev/pytest/issues/12624): The `pytest_plugins` variable and the `PYTEST_PLUGINS` environment variable now also accept entry point names of installed plugins (e.g. `xdist`), in addition to importable module names, matching the behavior of the `-p` command-line option. As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the `plugins:` line of the terminal header (`12615`). Based on the original implementation by Marcel Telka in `12616`. - [#12697](https://github.com/pytest-dev/pytest/issues/12697): Warnings emitted while importing plugins through `-p`, `PYTEST_PLUGINS`, or entry point autoloading are now captured, filtered, and reported like other warnings. - [#12860](https://github.com/pytest-dev/pytest/issues/12860): Assertion diffs for `dict.items()` and `dict.keys()` comparisons (`>=`, `<=`, `>`, `<`, `==`) now show which items are missing, the same way set comparisons do. - [#13354](https://github.com/pytest-dev/pytest/issues/13354): `Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker>` now also accepts a `~pytest.MarkDecorator` as its `default`, for example `item.get_closest_marker("foo", pytest.mark.foo(1))`, and returns the wrapped `~pytest.Mark`. Previously the only way to build a `default` was to instantiate `~pytest.Mark` directly, which is private and warns. - [#13369](https://github.com/pytest-dev/pytest/issues/13369): Improved the error from `pytest.RunResult.assert_outcomes` when a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins. - [#13431](https://github.com/pytest-dev/pytest/issues/13431): Exposed `pytest.ParameterSet` as the type of the return value of `pytest.param()`. This can be used in type annotations and `isinstance` checks. - [#13564](https://github.com/pytest-dev/pytest/issues/13564): Issue a warning when fixtures are wrapped with a decorator that prevents correct discovery, including `@classmethod` above `@pytest.fixture` and `@staticmethod` above `@pytest.fixture`. Put `@pytest.fixture` above those decorators on test classes. - [#14164](https://github.com/pytest-dev/pytest/issues/14164): Exposed `pytest.Approx` as the type of the return value of `pytest.approx()`. This can be used in type annotations and `isinstance` checks. - [#14463](https://github.com/pytest-dev/pytest/issues/14463): Assertion diffs for mappings now match up keys the way the compared mappings match them themselves. Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping with its own notion of key equivalence, such as case-insensitive header mappings, no longer reports its common keys as missing on either side. - [#14523](https://github.com/pytest-dev/pytest/issues/14523): Large assertion comparison diffs are now built lazily and capped to the truncation budget, so a huge diff is no longer formatted in full just to be truncated. As a consequence, the truncation footer no longer reports the exact number of hidden lines. - [#14687](https://github.com/pytest-dev/pytest/issues/14687): The default fd-level output capturing (`--capture=fd`) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites. - [#14724](https://github.com/pytest-dev/pytest/issues/14724): `--no-summary` now only applies directly to pytest's own summary. The flag no longer skips the `pytest_terminal_summary` hook, so third-party plugins (for example coverage) can still write their terminal summaries. - [#14751](https://github.com/pytest-dev/pytest/issues/14751): `parser.addini <pytest.Parser.addini>` now also accepts type expressions for its `type` argument, in addition to the existing string tags: the plain Python types `str`, `bool`, `int`, `float`, a `Literal` of strings, and unions of these (for example `int | str` or `int | Literal["auto"]`). - [#14754](https://github.com/pytest-dev/pytest/issues/14754): `pytest.approx()` now rejects infinite relative tolerances for `datetime.timedelta` values with a clear `ValueError` instead of raising `OverflowError`. - [#14791](https://github.com/pytest-dev/pytest/issues/14791): The `junit_family`, `junit_logging`, `junit_duration_report`, `console_output_style`, `empty_parameter_set_mark`, `assertion_text_diff_style` and `tmp_path_retention_policy` configuration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, and `pytest --help` lists the accepted values. `config.getini <pytest.Config.getini>` now raises `pytest.UsageError` instead of `TypeError` or `ValueError` when the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raises `ValueError`. - [#15006](https://github.com/pytest-dev/pytest/issues/15006): `pytest.approx` now emits `pytest.PytestApproxDecimalToleranceWarning` when a `rel` or `abs` tolerance is given as a `float` that cannot be represented exactly for a `~decimal.Decimal` comparison, since such a tolerance is widened to the float's exact binary value. - [#14675](https://github.com/pytest-dev/pytest/issues/14675), [#14953](https://github.com/pytest-dev/pytest/issues/14953), [#15153](https://github.com/pytest-dev/pytest/issues/15153), [#15132](https://github.com/pytest-dev/pytest/issues/15132): The `truncation_limit_lines`, `truncation_limit_chars`, `max_warnings`, `verbosity_assertions`, `verbosity_test_cases`, `verbosity_subtests`, `tmp_path_retention_count`, `log_level`, `log_cli_level`, `log_file_level`,`log_auto_indent` and `faulthandler_timeout` configuration options now accept native integer (and, for `log_auto_indent`, boolean) values in TOML configuration files, while still accepting strings for backward compatibility. `log_file_mode` now reports invalid values as a usage error. - [#15254](https://github.com/pytest-dev/pytest/issues/15254): `tmp_path` and `TempPathFactory.mktemp <pytest.TempPathFactory.mktemp>` no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist. - [#4569](https://github.com/pytest-dev/pytest/issues/4569): `Node.add_marker <_pytest.nodes.Node.add_marker>` now stores a `~pytest.Mark` in `node.keywords`, matching what marks applied during collection store. Previously it stored a `~pytest.MarkDecorator`. - [#9436](https://github.com/pytest-dev/pytest/issues/9436): Avoided formatting tracebacks for tests marked with `xfail(run=False)`. #### Bug fixes - [#10128](https://github.com/pytest-dev/pytest/issues/10128): Configured warning filters now apply to warnings emitted by `pytest_configure` hooks. - [#10210](https://github.com/pytest-dev/pytest/issues/10210): `pytest.approx` now raises a `TypeError` for any nested container, not only for one of the same type as its parent. Previously `approx([{"k": 1}])` and `approx({"k": [1]})` were accepted and then compared unequal to every value, silently ignoring the tolerance, while `approx([[1]])` correctly reported that nesting is unsupported. - [#10644](https://github.com/pytest-dev/pytest/issues/10644): `monkeypatch.setattr()` no longer leaves a new entry in the instance `__dict__` when it patches an attribute that the instance inherits from its class. Previously `undo()` assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically. - [#1139](https://github.com/pytest-dev/pytest/issues/1139): Fixed tracebacks showing `???` instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root. The source lookup now falls back to searching `sys.path` for such filenames, as the standard `traceback` module does. - [#11502](https://github.com/pytest-dev/pytest/issues/11502): The `rootdir` is no longer derived from a configuration file that is not a regular file, such as `--config-file=/dev/null`. - [#11783](https://github.com/pytest-dev/pytest/issues/11783): Plugins installed in editable mode (`660`) are marked for assertion rewriting again. Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case. - [#11933](https://github.com/pytest-dev/pytest/issues/11933): `pytest.warns` no longer re-emits unmatched warnings with `module="warnings"`, which caused `module`-based warning filters to be applied to the wrong warnings. Since `warnings.WarningMessage` does not record the module a warning was emitted with, re-emitted warnings now use the standard `warnings.warn_explicit` default of deriving the module from the warning's filename. - [#12175](https://github.com/pytest-dev/pytest/issues/12175): `ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly>` now strips the `AssertionError:` prefix of failed `assert` statements for `~pytest.ExceptionInfo` objects created by `pytest.raises`, and failures inside `unittest.TestCase.subTest` report the same short crash line as regular tests. - [#12223](https://github.com/pytest-dev/pytest/issues/12223): The `message` attribute of `<failure>` and `<error>` elements in `--junitxml` reports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with `-vv`) produced attributes tens of thousands of characters long, which some XML parsers fail on. - [#12307](https://github.com/pytest-dev/pytest/issues/12307): Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in `assert condition, msg`) when using `-vv`: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with `...`. - [#12824](https://github.com/pytest-dev/pytest/issues/12824): Custom command-line options now fail with a clear error when their implicit destination conflicts with an existing option, avoiding silent overrides of built-in options such as `-k`. - [#13292](https://github.com/pytest-dev/pytest/issues/13292): Fixed a stale rewritten module being used when a test file is modified twice within the same second without changing its size -- the pyc header could only record whole-second timestamps. The cache is now keyed on a hash of the source. - [#14036](https://github.com/pytest-dev/pytest/issues/14036): `__tracebackhide__` is now respected in `ExceptionGroup` tracebacks, both for the group itself and for its sub-exceptions. - [#14189](https://github.com/pytest-dev/pytest/issues/14189): Nested usage of `caplog.filtering <pytest.LogCaptureFixture.filtering>` no longer removes filters early if they were already present. - [#14412](https://github.com/pytest-dev/pytest/issues/14412): Fixed incorrect timing information for subtests and parent tests when `console_output_style = "times"`. - [#14445](https://github.com/pytest-dev/pytest/issues/14445): Assertion rewriting no longer evaluates walrus operator (`:=`) expressions more than once, which reported results the test never computed when the expression had side effects. An operand evaluated before a later walrus is now reported with the value it actually saw, so `assert value != identity(value := value.lower())` keeps Python's left-to-right order. - [#14552](https://github.com/pytest-dev/pytest/issues/14552): Fixed stale `co_filename` values after a test module or directory is moved. Assertion-rewrite caches are reused when the source hash still matches, and in-memory code objects are pointed at the current path. - [#14586](https://github.com/pytest-dev/pytest/issues/14586): Negative values passed to `log_auto_indent` now correctly fall back to no indentation, matching the documented behavior. - [#14619](https://github.com/pytest-dev/pytest/issues/14619): Fixed a crash in `pytest.mark.parametrize` when a non-sequence value is passed for a parameter set. It now provides a clear error message during collection. - [#14635](https://github.com/pytest-dev/pytest/issues/14635): Fixed fixture resolution failures when specifying multiple test paths on the command line that share common parent directories. Parametrized fixtures defined in a `conftest.py` could be silently dropped depending on the order of the specified paths. - [#14637](https://github.com/pytest-dev/pytest/issues/14637): Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning. - [#14638](https://github.com/pytest-dev/pytest/issues/14638): Top-level options in `pytest.toml` and `.pytest.toml` files now raise an error instead of being silently ignored when no `[pytest]` table is present. - [#14683](https://github.com/pytest-dev/pytest/issues/14683): Fixed a regression in pytest 9.1 where a conftest.py located in the rootdir was no longer visible to tests and doctests collected from *outside* the rootdir (for example when passing a parent directory of the rootdir as a collection argument, or setting `--rootdir` to a subdirectory). As a result, fixtures defined in such a conftest -- including `doctest_namespace` injections -- were not available, causing errors such as `NameError` in doctests. - [#14700](https://github.com/pytest-dev/pytest/issues/14700): Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped. - [#14705](https://github.com/pytest-dev/pytest/issues/14705): TOML configuration files passed via `-c` now also read their configuration from the `[pytest]` table, the one pytest's own configuration files use. The `[tool.pytest]` and `[tool.pytest.ini_options]` tables such files were previously restricted to keep working; using both styles in one file is an error. - [#14828](https://github.com/pytest-dev/pytest/issues/14828): Exception groups raised from another exception now print their cause chain only once in the traceback output. - [#14864](https://github.com/pytest-dev/pytest/issues/14864): Fixed collection on Windows collecting the whole suite instead of the given path, on file systems which do not support file IDs (`st_ino` is `0` for every file, as seen for example on `sshfs-win`/WinFsp mounts). - [#14884](https://github.com/pytest-dev/pytest/issues/14884): `Cache.get()`, `Cache.set()` and `Cache.mkdir()` now reject keys that resolve outside the cache directory, and `--cache-show` ignores glob matches outside it. - [#14909](https://github.com/pytest-dev/pytest/issues/14909): Fixed `MonkeyPatch.delattr <pytest.MonkeyPatch.delattr>`, `MonkeyPatch.setitem <pytest.MonkeyPatch.setitem>` and `MonkeyPatch.delitem <pytest.MonkeyPatch.delitem>` recording a stale undo entry when the underlying mutation failed, which could cause spurious errors during teardown. The undo entry is now recorded only after the mutation succeeds, matching the behavior of `MonkeyPatch.setattr <pytest.MonkeyPatch.setattr>`. - [#14912](https://github.com/pytest-dev/pytest/issues/14912): `~pytest.PytestWarning` instances defined in `_pytest.deprecated` are no longer reused across `warnings.warn` calls, so warnings raised as errors (e.g. with `-W error`) no longer accumulate stale traceback frames from previous raises. - [#14942](https://github.com/pytest-dev/pytest/issues/14942): Fixed a regression in 9.1.0 that made collection very slow (quadratic) when many fixtures are defined with the same name. This can happen particularly when many tests are defined in separate classes which inherit from a base class which defines fixtures (the fixtures are repeated per class). - [#15005](https://github.com/pytest-dev/pytest/issues/15005): `pytest.approx` no longer treats finite `~decimal.Decimal` values outside the `float` range (such as `Decimal("1e400")`) as infinite, which made in-tolerance comparisons fail. - [#15006](https://github.com/pytest-dev/pytest/issues/15006): Restored the tolerance shown by `pytest.approx` for `~decimal.Decimal` values, which since 9.0 displayed `???` for the default tolerance and reported the raw `rel` ratio instead of the absolute tolerance actually compared against. - [#15006](https://github.com/pytest-dev/pytest/issues/15006): The failure message for `pytest.approx` comparisons of `~decimal.Decimal` collections no longer reports `Max absolute difference: -inf`, or crashes for mappings, when the `decimal.FloatOperation` trap is set. - [#15006](https://github.com/pytest-dev/pytest/issues/15006): `pytest.approx` no longer raises `AttributeError` when comparing `numpy.ndarray` instances with `object` dtype, such as arrays of `~decimal.Decimal`. - [#15032](https://github.com/pytest-dev/pytest/issues/15032): Help texts for command-line options and configuration options now keep their indentation and blank lines. Previously each line was stripped before wrapping, so a wrapped list item was indistinguishable from a new one and blank lines were dropped; configuration option help lost its line breaks entirely. - [#15043](https://github.com/pytest-dev/pytest/issues/15043): Cache writes now emit `pytest.PytestCacheWarning` when writing or closing the cache file fails, consistent with errors opening the file. - [#15052](https://github.com/pytest-dev/pytest/issues/15052): Fixed possible off-by-one line numbers in `--fixtures` and `--fixtures-per-test` output. - [#15145](https://github.com/pytest-dev/pytest/issues/15145): With `console_output_style` set to `times`, durations just below a unit boundary are now shown in the next unit (e.g. `1.000ms` instead of `1000.0us`). - [#15172](https://github.com/pytest-dev/pytest/issues/15172): Assertion diffs now pretty-print the built-in `frozendict` (Python 3.15+) across multiple lines, similarly to how `dict` is displayed. - [#4569](https://github.com/pytest-dev/pytest/issues/4569): `-k` no longer matches attributes that end up in a test function's `__dict__` without being meant as keywords, such as pytest's own `pytestmark` attribute and the bookkeeping left behind by `functools.wraps` and `functools.lru_cache`. - [#6750](https://github.com/pytest-dev/pytest/issues/6750): Fix fixture argument discovery for custom collectors that pass bound methods to `pytest.Function`. - [#6997](https://github.com/pytest-dev/pytest/issues/6997): XFAIL reports from teardown phases now include the phase in the short test summary. - [#7940](https://github.com/pytest-dev/pytest/issues/7940): Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed. - [#8321](https://github.com/pytest-dev/pytest/issues/8321): Fixed exception chains being duplicated in the traceback output when an exception in the chain (`__cause__`/`__context__`) has no traceback of its own, and that exception is itself linked to further exceptions. - [#8914](https://github.com/pytest-dev/pytest/issues/8914): Tests parametrized with higher-than-function scope are now reordered by parameter *value* rather than by parameter *index*, so that items using equal parameter values are grouped together and share a single fixture setup, even when they are parametrized by separate `@pytest.mark.parametrize <pytest.mark.parametrize ref>` calls. Previously, an expensive higher-scoped fixture could be set up and torn down repeatedly for the same parameter value. Unhashable parameter values (e.g. dicts) keep the previous index-based grouping behavior. As a consequence, the order in which parametrized tests run may change (fixture setup/teardown counts can only decrease, not increase). - [#9924](https://github.com/pytest-dev/pytest/issues/9924): Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure. #### Improved documentation - [#10721](https://github.com/pytest-dev/pytest/issues/10721): Replaced `setup.py` usage with `pyproject.toml` in `writing-plugins`. - [#12658](https://github.com/pytest-dev/pytest/issues/12658): Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation. - [#12857](https://github.com/pytest-dev/pytest/issues/12857): Documented how `--confcutdir` affects initial `conftest.py` discovery. - [#14157](https://github.com/pytest-dev/pytest/issues/14157): Added the `pytest-flakefighters` plugin to the list of flaky test plugins in `plugins.rst`. Added flaky test papers published on the [Test FLARE](https://test-flare.github.io/) project to the list of flaky papers in `plugins.rst`. - [#15127](https://github.com/pytest-dev/pytest/issues/15127): Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type. - [#15242](https://github.com/pytest-dev/pytest/issues/15242): The `installation instructions <installation>` and `install-package-with-pip` now show how to install pytest into a virtual environment with venv and pip, uv or virtualenv, and explain the `externally-managed-environment` error. - [#4569](https://github.com/pytest-dev/pytest/issues/4569): `pytest --help`, the `-k` reference entry and `select-tests` no longer describe `-k` as a Python expression matched against test names only; `keyword expressions` now shows marker names being matched as well. The examples that looked up a marker use `Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker>` rather than `item.keywords`. - [#9614](https://github.com/pytest-dev/pytest/issues/9614): Clarified that `session.items` and `session.testscollected` exclude deselected tests in the `pytest_collection` documentation. #### Packaging updates and notes for downstreams - [#11680](https://github.com/pytest-dev/pytest/issues/11680): Source archives of arbitrary commits -- the tarballs GitHub serves under `/archive/`, not just the ones for tags -- can now be built into an sdist or a wheel with a correct version. A `.git_archival.txt` file, expanded by `git archive` via `export-subst`, carries the describe output that `setuptools-scm` would otherwise have to ask `git` for. The archival file deliberately omits `ref-names`. Recording it would make the content of an archive -- and therefore its checksum -- change whenever a branch that points at the archived commit is moved afterwards, which is how the equivalent tarballs of tagged releases became unstable for other projects. Describe output alone depends only on the commit and on the tags reachable from it. The archival file is not shipped in the sdist -- an sdist carries its version in its metadata, and the template is only ever expanded by `git archive`. Building pytest from a git checkout now requires `setuptools-scm >= 10.1`. - [#9236](https://github.com/pytest-dev/pytest/issues/9236): `pluggy>=1.6` is now required. Older pluggy versions stopped running the remaining hook wrapper teardowns once an old-style `hookwrapper` raised in its own teardown. The logging plugin's wrapper was left suspended, and when it was finalised later it detached the handler that `caplog` of a subsequent test was recording through, so that test saw no records. #### Contributor-facing changes - [#14813](https://github.com/pytest-dev/pytest/issues/14813): Added a systematic coverage matrix for assertion rewriting. - [#14921](https://github.com/pytest-dev/pytest/issues/14921): Added scripts/diff-assert-rewrite.py, which diffs the assert-rewritten form of a snippet between the plain source, this checkout and released pytest versions. - [#15190](https://github.com/pytest-dev/pytest/issues/15190): Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented `DistFacade` compatibility class. #### Miscellaneous internal changes - [#13888](https://github.com/pytest-dev/pytest/issues/13888): `FixtureRequest.node <pytest.FixtureRequest.node>` is now explicitly annotated as returning `Any`, so strict pyright no longer reports it as `Unknown`. The return type stays deliberately broad, see `13888`. - [#14758](https://github.com/pytest-dev/pytest/issues/14758): Internal node ids (the `::`-separated strings identifying collected items, e.g. `path/to/test_file.py::TestClass::test_method[param]`) are now represented internally by a single structured `~_pytest.nodeid.NodeId` dataclass instead of being repeatedly re-parsed as plain strings. The public `nodeid: str` attribute on nodes and reports is unchanged and remains fully backward compatible for plugins. ### [`v9.1.1`](https://github.com/pytest-dev/pytest/releases/tag/9.1.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/9.1.0...9.1.1) ### pytest 9.1.1 (2026-06-19) #### Bug fixes - [#14220](https://github.com/pytest-dev/pytest/issues/14220): Fixed a logic bug in `pytest.RaisesGroup` which would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages. - [#14591](https://github.com/pytest-dev/pytest/issues/14591): Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect [@pytest](https://github.com/pytest).mark.parametrize to fail with "duplicate parametrization of '\<fixture name>'". - [#14606](https://github.com/pytest-dev/pytest/issues/14606): Fixed `list-item` typing errors from mypy in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` `argvalues` parameter. - [#14608](https://github.com/pytest-dev/pytest/issues/14608): Fixed a regression in pytest 9.1.0 where `conftest.py` files located in `<invocation dir>/test*` were no longer loaded as initial conftests when invoked without arguments. This could cause certain hooks (like `pytest_addoption`) in these files to not fire. ### [`v9.1.0`](https://github.com/pytest-dev/pytest/releases/tag/9.1.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/9.0.3...9.1.0) ### pytest 9.1.0 (2026-06-13) #### Removals and backward incompatible breaking changes - [#14533](https://github.com/pytest-dev/pytest/issues/14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice. If this is undesirable, move the fixture definition to a `conftest.py` file if possible. Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`. This means that both need to register the fixtures independently. #### Deprecations (removal in next major release) - [#10819](https://github.com/pytest-dev/pytest/issues/10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`. See `10819` and `14011`. - [#12882](https://github.com/pytest-dev/pytest/issues/12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10. See `dynamic-fixture-request-during-teardown` for details. - [#13409](https://github.com/pytest-dev/pytest/issues/13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated. These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times, using class-level parametrize decorators, or collecting tests multiple times. See `parametrize-iterators` for details and suggestions. - [#13946](https://github.com/pytest-dev/pytest/issues/13946): The private `config.inicfg` attribute is now deprecated. Use `config.getini() <pytest.Config.getini>` to access configuration values instead. See `config-inicfg` for more details. - [#14004](https://github.com/pytest-dev/pytest/issues/14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins. Use the `node` parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used `nodeid=None`, pass `node=session` instead. This will be removed in pytest 10. - [#14335](https://github.com/pytest-dev/pytest/issues/14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See `hook-markers` for more details. - [#14434](https://github.com/pytest-dev/pytest/issues/14434): The `--pastebin` option is now deprecated. The same functionality is now available in an external plugin, `pytest-pastebin`. See `pastebin-deprecated` for more details. - [#14513](https://github.com/pytest-dev/pytest/issues/14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10. See `fixturedef-has-location-deprecated` for details. - [#1764](https://github.com/pytest-dev/pytest/issues/1764): `pytest.console_main` is now deprecated and will be removed in pytest 10. It was never intended for programmatic use; use `pytest.main` instead. #### New features - [#12376](https://github.com/pytest-dev/pytest/issues/12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface. This is an advanced function intended for use by plugins. Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator. Pytest looks for these fixture definitions during the collection phase and registers them automatically. For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used. - [#14023](https://github.com/pytest-dev/pytest/issues/14023): Added --report-chars long CLI option. - [#14371](https://github.com/pytest-dev/pytest/issues/14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`. - [#6757](https://github.com/pytest-dev/pytest/issues/6757): Added the `assertion_text_diff_style` configuration option, allowing string equality failures to be rendered as separate `Left:` and `Right:` blocks instead of `ndiff` output. - [#8395](https://github.com/pytest-dev/pytest/issues/8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`. #### Improvements in existing functionality - [#11225](https://github.com/pytest-dev/pytest/issues/11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match. - [#11295](https://github.com/pytest-dev/pytest/issues/11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar. - [#13241](https://github.com/pytest-dev/pytest/issues/13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters. `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept. - [#13862](https://github.com/pytest-dev/pytest/issues/13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr. - [#14026](https://github.com/pytest-dev/pytest/issues/14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter. - [#14137](https://github.com/pytest-dev/pytest/issues/14137): pytest.ScopeName is now public to allow using it in function signatures. - [#14342](https://github.com/pytest-dev/pytest/issues/14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already. - [#14373](https://github.com/pytest-dev/pytest/issues/14373): Added type annotations for `pytest.approx`. - [#14430](https://github.com/pytest-dev/pytest/issues/14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result. - [#14441](https://github.com/pytest-dev/pytest/issues/14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs. - [#14461](https://github.com/pytest-dev/pytest/issues/14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances. - [#14513](https://github.com/pytest-dev/pytest/issues/14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered. A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later. Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins". This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name. - [#14524](https://github.com/pytest-dev/pytest/issues/14524): Add official Python 3.15 support. - [#1764](https://github.com/pytest-dev/pytest/issues/1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer. - [#8265](https://github.com/pytest-dev/pytest/issues/8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`. Previously this caused a cryptic `TypeError: got None instead of Mark` error. Now pytest issues a helpful warning and continues collecting the module normally. #### Bug fixes - [#13192](https://github.com/pytest-dev/pytest/issues/13192): Fixed | (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`. - [#13484](https://github.com/pytest-dev/pytest/issues/13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`. - [#13626](https://github.com/pytest-dev/pytest/issues/13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit, allowing them to potentially be released more promptly. - [#13784](https://github.com/pytest-dev/pytest/issues/13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`). - [#13817](https://github.com/pytest-dev/pytest/issues/13817): Fixed a secondary AttributeError masking the original error when an option argument fails to initialize. - [#13884](https://github.com/pytest-dev/pytest/issues/13884): Fixed rare internal IndexError caused by builtins.compile being overridden in client code. - [#13885](https://github.com/pytest-dev/pytest/issues/13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0. - [#13917](https://github.com/pytest-dev/pytest/issues/13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it. - [#13963](https://github.com/pytest-dev/pytest/issues/13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable. Fixes [pytest-dev/pytest-xdist#1273](https://github.com/pytest-dev/pytest-xdist/issues/1273). - [#14004](https://github.com/pytest-dev/pytest/issues/14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`. Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories when using a relative `testpaths` like `../tests/sdk`. Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping. - [#14050](https://github.com/pytest-dev/pytest/issues/14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order. - [#14080](https://github.com/pytest-dev/pytest/issues/14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods. - [#14114](https://github.com/pytest-dev/pytest/issues/14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests. - [#14161](https://github.com/pytest-dev/pytest/issues/14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown. - [#14214](https://github.com/pytest-dev/pytest/issues/14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated. - [#14234](https://github.com/pytest-dev/pytest/issues/14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing. - [#14248](https://github.com/pytest-dev/pytest/issues/14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures. - [#14263](https://github.com/pytest-dev/pytest/issues/14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order. - [#14377](https://github.com/pytest-dev/pytest/issues/14377): Fixed crash in Config.get_terminal_writer when an assertion fails with the `terminalreporter` plugin disabled. - [#14381](https://github.com/pytest-dev/pytest/issues/14381): Fixed `-V` (short form of `--version`) to properly display the current version. - [#14389](https://github.com/pytest-dev/pytest/issues/14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`. - [#14392](https://github.com/pytest-dev/pytest/issues/14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead. - [#14442](https://github.com/pytest-dev/pytest/issues/14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored. Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`. - [#14456](https://github.com/pytest-dev/pytest/issues/14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays. - [#14474](https://github.com/pytest-dev/pytest/issues/14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping. - [#14483](https://github.com/pytest-dev/pytest/issues/14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights` - [#14492](https://github.com/pytest-dev/pytest/issues/14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`. - [#3697](https://github.com/pytest-dev/pytest/issues/3697): Logging capture now works for non-propagating loggers. Previously only logs which reached the root logger were captured. This includes `caplog` and the "Captured log calls" test reporting. - [#3850](https://github.com/pytest-dev/pytest/issues/3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file. - [#5848](https://github.com/pytest-dev/pytest/issues/5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases. - [#719](https://github.com/pytest-dev/pytest/issues/719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`). The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack. #### Improved documentation - [#11022](https://github.com/pytest-dev/pytest/issues/11022): Document safer alternatives and scope guidance for monkeypatching standard library functions. - [#11307](https://github.com/pytest-dev/pytest/issues/11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`. - [#13038](https://github.com/pytest-dev/pytest/issues/13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures. - [#13155](https://github.com/pytest-dev/pytest/issues/13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`. - [#13304](https://github.com/pytest-dev/pytest/issues/13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options. - [#13902](https://github.com/pytest-dev/pytest/issues/13902): Clarified how subtest progress markers are shown in the documentation. - [#14012](https://github.com/pytest-dev/pytest/issues/14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option. - [#14148](https://github.com/pytest-dev/pytest/issues/14148): Documented a safe `pytestconfig.cache` access pattern when the `cacheprovider` plugin is disabled. - [#14303](https://github.com/pytest-dev/pytest/issues/14303): The documentation is now built with Sphinx >= 9. - [#14465](https://github.com/pytest-dev/pytest/issues/14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on. #### Miscellaneous internal changes - [#14582](https://github.com/pytest-dev/pytest/issues/14582): Improved the recursion traceback test to exercise all requested traceback styles. ### [`v9.0.3`](https://github.com/pytest-dev/pytest/releases/tag/9.0.3) [Compare Source](https://github.com/pytest-dev/pytest/compare/9.0.2...9.0.3) ### pytest 9.0.3 (2026-04-07) #### Bug fixes - [#12444](https://github.com/pytest-dev/pytest/issues/12444): Fixed `pytest.approx` which now correctly takes into account `~collections.abc.Mapping` keys order to compare them. - [#13634](https://github.com/pytest-dev/pytest/issues/13634): 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](https://github.com/pytest-dev/pytest/issues/13734): Fixed crash when a test raises an exceptiongroup with `__tracebackhide__ = True`. - [#14195](https://github.com/pytest-dev/pytest/issues/14195): Fixed an issue where non-string messages passed to unittest.TestCase.subTest() were not printed. - [#14343](https://github.com/pytest-dev/pytest/issues/14343): Fixed use of insecure temporary directory (CVE-2025-71176). #### Improved documentation - [#13388](https://github.com/pytest-dev/pytest/issues/13388): Clarified documentation for `-p` vs `PYTEST_PLUGINS` plugin loading and fixed an incorrect `-p` example. - [#13731](https://github.com/pytest-dev/pytest/issues/13731): Clarified that capture fixtures (e.g. `capsys` and `capfd`) take precedence over the `-s` / `--capture=no` command-line options in `Accessing captured output from a test function <accessing-captured-output>`. - [#14088](https://github.com/pytest-dev/pytest/issues/14088): Clarified that the default `pytest_collection` hook sets `session.items` before it calls `pytest_collection_finish`, not after. - [#14255](https://github.com/pytest-dev/pytest/issues/14255): TOML integer log levels must be quoted: Updating reference documentation. #### Contributor-facing changes - [#12689](https://github.com/pytest-dev/pytest/issues/12689): The test reports are now published to Codecov from GitHub Actions. The test statistics is visible [on the web interface](https://app.codecov.io/gh/pytest-dev/pytest/tests). \-- by `aleguy02` ### [`v9.0.2`](https://github.com/pytest-dev/pytest/releases/tag/9.0.2) [Compare Source](https://github.com/pytest-dev/pytest/compare/9.0.1...9.0.2) ### pytest 9.0.2 (2025-12-06) #### Bug fixes - [#13896](https://github.com/pytest-dev/pytest/issues/13896): 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](https://github.com/pytest-dev/pytest/issues/13904): Fixed the TOML type of the `tmp_path_retention_count` settings in the API reference from number to string. - [#13946](https://github.com/pytest-dev/pytest/issues/13946): 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](https://github.com/pytest-dev/pytest/issues/13965): Fixed quadratic-time behavior when handling `unittest` subtests in Python 3.10. #### Improved documentation - [#4492](https://github.com/pytest-dev/pytest/issues/4492): The API Reference now contains cross-reference-able documentation of `pytest's command-line flags <command-line-flags>`. ### [`v9.0.1`](https://github.com/pytest-dev/pytest/releases/tag/9.0.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/9.0.0...9.0.1) ### pytest 9.0.1 (2025-11-12) #### Bug fixes - [#13895](https://github.com/pytest-dev/pytest/issues/13895): Restore support for skipping tests via `raise unittest.SkipTest`. - [#13896](https://github.com/pytest-dev/pytest/issues/13896): 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](https://github.com/pytest-dev/pytest/issues/13904): Fixed the TOML type of the verbosity settings in the API reference from number to string. - [#13910](https://github.com/pytest-dev/pytest/issues/13910): 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](https://github.com/pytest-dev/pytest/issues/13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. #### Contributor-facing changes - [#13891](https://github.com/pytest-dev/pytest/issues/13891), [#13942](https://github.com/pytest-dev/pytest/issues/13942): The CI/CD part of the release automation is now capable of creating GitHub Releases without having a Git checkout on disk -- by `bluetech` and `webknjaz`. - [#13933](https://github.com/pytest-dev/pytest/issues/13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. ### [`v9.0.0`](https://github.com/pytest-dev/pytest/releases/tag/9.0.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.4.2...9.0.0) ### pytest 9.0.0 (2025-11-05) #### New features - [#1367](https://github.com/pytest-dev/pytest/issues/1367): **Support for subtests** has been added. `subtests <subtests>` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time. Example: ```python def contains_docstring(p: Path) -> bool: """Return True if the given Python file contains a top-level docstring.""" ... def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None: for path in Path.cwd().glob("*.py"): 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, `unittest.TestCase.subTest` is now also supported. This feature was originally implemented as a separate plugin in [pytest-subtests](https://github.com/pytest-dev/pytest-subtests), 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](https://github.com/pytest-dev/pytest/issues/13743): 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 "INI compatibility mode", 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. ```toml # pyproject.toml [tool.pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` 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't use `pyproject.toml`, you can use `pytest.toml` or `.pytest.toml`: ```toml # pytest.toml or .pytest.toml [pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface. See `config file formats` for full details. - [#13823](https://github.com/pytest-dev/pytest/issues/13823): Added a **"strict mode"** enabled by the `strict` configuration option. When set to `true`, the `strict` option currently enables - `strict_config` - `strict_markers` - `strict_parametrization_ids` - `strict_xfail` The individual strictness options can be explicitly set to override the global `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 `strict mode` for more details. - [#13737](https://github.com/pytest-dev/pytest/issues/13737): Added the `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](https://github.com/pytest-dev/pytest/issues/13072): Added support for displaying test session **progress in the terminal tab** using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC) ANSI sequence. When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty, you'll see the progress in the terminal tab or window, allowing you to monitor pytest'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='-p no:terminalprogress'`. - On a project configuration level, using `addopts = "-p no:terminalprogress"`. - [#478](https://github.com/pytest-dev/pytest/issues/478): Support PEP420 (implicit namespace packages) as --pyargs target when `consider_namespace_packages` is true in the config. Previously, this option only impacted package imports, now it also impacts tests discovery. - [#13678](https://github.com/pytest-dev/pytest/issues/13678): Added a new `faulthandler_exit_on_timeout` configuration option set to "false" 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 `ogrisel`. - [#13829](https://github.com/pytest-dev/pytest/issues/13829): Added support for configuration option aliases via the `aliases` parameter in `Parser.addini() <pytest.Parser.addini>`. 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](https://github.com/pytest-dev/pytest/issues/13330): 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 `sgaist` - [#13574](https://github.com/pytest-dev/pytest/issues/13574): 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 `PYTEST_ADDOPTS` or `addopts`. - [#13823](https://github.com/pytest-dev/pytest/issues/13823): Added `strict_xfail` as an alias to the `xfail_strict` option, `strict_config` as an alias to the `--strict-config` flag, and `strict_markers` as an alias to the `--strict-markers` flag. This makes all strictness options consistently have configuration options with the prefix `strict_`. - [#13700](https://github.com/pytest-dev/pytest/issues/13700): --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given. - [#13732](https://github.com/pytest-dev/pytest/issues/13732): 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](https://github.com/pytest-dev/pytest/issues/13859): Clarify the error message for pytest.raises() when a regex match fails. - [#13861](https://github.com/pytest-dev/pytest/issues/13861): Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be \<expected>, but got \<actual>". Now, it is "Expected \<expected>, but got \<actual>". #### Removals and backward incompatible breaking changes - [#12083](https://github.com/pytest-dev/pytest/issues/12083): 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 `--keep-duplicates <duplicate-paths>`, which retains its existing behavior (including the bug). - [#13719](https://github.com/pytest-dev/pytest/issues/13719): Support for Python 3.9 is dropped following its end of life. - [#13766](https://github.com/pytest-dev/pytest/issues/13766): 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. - [#13779](https://github.com/pytest-dev/pytest/issues/13779): **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 `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: ```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 `13779`. #### Deprecations (removal in next major release) - [#13807](https://github.com/pytest-dev/pytest/issues/13807): `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` 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 (`420`). See `monkeypatch-fixup-namespace-packages` for details. #### Bug fixes - [#13445](https://github.com/pytest-dev/pytest/issues/13445): Made the type annotations of `pytest.skip` and friends more spec-complaint to have them work across more type checkers. - [#13537](https://github.com/pytest-dev/pytest/issues/13537): Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in teardown was not handled correctly and showed as error. - [#13598](https://github.com/pytest-dev/pytest/issues/13598): Fixed possible collection confusion on Windows when short paths and symlinks are involved. - [#13716](https://github.com/pytest-dev/pytest/issues/13716): 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](https://github.com/pytest-dev/pytest/issues/13722): Fixed a misleading assertion failure message when using `pytest.approx` on mappings with differing lengths. - [#13773](https://github.com/pytest-dev/pytest/issues/13773): Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures. - [#13816](https://github.com/pytest-dev/pytest/issues/13816): Fixed `pytest.approx` which now returns a clearer error message when comparing mappings with different keys. - [#13849](https://github.com/pytest-dev/pytest/issues/13849): 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](https://github.com/pytest-dev/pytest/issues/13865): Fixed --show-capture with --tb=line. - [#13522](https://github.com/pytest-dev/pytest/issues/13522): Fixed `pytester` in subprocess mode ignored all :attr\`pytester.plugins \<pytest.Pytester.plugins>\` except the first. Fixed `pytester` in subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`. Now it errors instead. If you are affected by this, specify the plugin by name, or switch the affected tests to use `pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess>` explicitly instead. #### Packaging updates and notes for downstreams - [#13791](https://github.com/pytest-dev/pytest/issues/13791): Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1` and `22.0.0`, respectively. #### Contributor-facing changes - [#12244](https://github.com/pytest-dev/pytest/issues/12244): Fixed self-test failures when TERM=dumb. - [#12474](https://github.com/pytest-dev/pytest/issues/12474): Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation. - [#13621](https://github.com/pytest-dev/pytest/issues/13621): pytest'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](https://github.com/pytest-dev/pytest/issues/13638): Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`. The script now uses `gh pr create` which is compatible with GitHub CLI v2.0+. - [#13695](https://github.com/pytest-dev/pytest/issues/13695): Flush stdout and stderr in Pytester.run to avoid truncated outputs in test_faulthandler.py::test_timeout on CI -- by `ogrisel`. - [#13771](https://github.com/pytest-dev/pytest/issues/13771): Skip test_do_not_collect_symlink_siblings on Windows environments without symlink support to avoid false negatives. - [#13841](https://github.com/pytest-dev/pytest/issues/13841): `tox>=4` is now required when contributing to pytest. - [#13625](https://github.com/pytest-dev/pytest/issues/13625): Added missing docstrings to `pytest_addoption()`, `pytest_configure()`, and `cacheshow()` functions in `cacheprovider.py`. #### Miscellaneous internal changes - [#13830](https://github.com/pytest-dev/pytest/issues/13830): Configuration overrides (`-o`/`--override-ini`) are now processed during startup rather than during `config.getini() <pytest.Config.getini>`. ### [`v8.4.2`](https://github.com/pytest-dev/pytest/releases/tag/8.4.2) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.4.1...8.4.2) ### pytest 8.4.2 (2025-09-03) #### Bug fixes - [#13478](https://github.com/pytest-dev/pytest/issues/13478): Fixed a crash when using `console_output_style`{.interpreted-text role="confval"} with `times` and a module is skipped. - [#13530](https://github.com/pytest-dev/pytest/issues/13530): Fixed a crash when using `pytest.approx`{.interpreted-text role="func"} and `decimal.Decimal`{.interpreted-text role="class"} instances with the `decimal.FloatOperation`{.interpreted-text role="class"} trap set. - [#13549](https://github.com/pytest-dev/pytest/issues/13549): No longer evaluate type annotations in Python `3.14` when inspecting function signatures. This prevents crashes during module collection when modules do not explicitly use `from __future__ import annotations` and import types for annotations within a `if TYPE_CHECKING:` block. - [#13559](https://github.com/pytest-dev/pytest/issues/13559): Added missing \[int]{.title-ref} and \[float]{.title-ref} variants to the \[Literal]{.title-ref} type annotation of the \[type]{.title-ref} parameter in `pytest.Parser.addini`{.interpreted-text role="meth"}. - [#13563](https://github.com/pytest-dev/pytest/issues/13563): `pytest.approx`{.interpreted-text role="func"} now only imports `numpy` if NumPy is already in `sys.modules`. This fixes unconditional import behavior introduced in \[8.4.0]{.title-ref}. #### Improved documentation - [#13577](https://github.com/pytest-dev/pytest/issues/13577): Clarify that `pytest_generate_tests` is discovered in test modules/classes; other hooks must be in `conftest.py` or plugins. #### Contributor-facing changes - [#13480](https://github.com/pytest-dev/pytest/issues/13480): Self-testing: fixed a few test failures when run with `-Wdefault` or a similar override. - [#13547](https://github.com/pytest-dev/pytest/issues/13547): Self-testing: corrected expected message for `test_doctest_unexpected_exception` in Python `3.14`. - [#13684](https://github.com/pytest-dev/pytest/issues/13684): Make pytest's own testsuite insensitive to the presence of the `CI` environment variable -- by `ogrisel`{.interpreted-text role="user"}. ### [`v8.4.1`](https://github.com/pytest-dev/pytest/releases/tag/8.4.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.4.0...8.4.1) ### pytest 8.4.1 (2025-06-17) #### Bug fixes - [#13461](https://github.com/pytest-dev/pytest/issues/13461): Corrected `_pytest.terminal.TerminalReporter.isatty` to support being called as a method. Before it was just a boolean which could break correct code when using `-o log_cli=true`). - [#13477](https://github.com/pytest-dev/pytest/issues/13477): Reintroduced `pytest.PytestReturnNotNoneWarning`{.interpreted-text role="class"} which was removed by accident in pytest \[8.4]{.title-ref}. This warning is raised when a test functions returns a value other than `None`, which is often a mistake made by beginners. See `return-not-none`{.interpreted-text role="ref"} for more information. - [#13497](https://github.com/pytest-dev/pytest/issues/13497): Fixed compatibility with `Twisted 25+`. #### Improved documentation - [#13492](https://github.com/pytest-dev/pytest/issues/13492): Fixed outdated warning about `faulthandler` not working on Windows. ### [`v8.4.0`](https://github.com/pytest-dev/pytest/releases/tag/8.4.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.3.5...8.4.0) ### pytest 8.4.0 (2025-06-02) #### Removals and backward incompatible breaking changes - [#11372](https://github.com/pytest-dev/pytest/issues/11372): Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed. - [#12346](https://github.com/pytest-dev/pytest/issues/12346): Tests will now fail, instead of raising a warning, if they return any value other than None. - [#12874](https://github.com/pytest-dev/pytest/issues/12874): We dropped support for Python 3.8 following its end of life (2024-10-07). - [#12960](https://github.com/pytest-dev/pytest/issues/12960): Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning. See `the docs <yield tests deprecated>`{.interpreted-text role="ref"} for more information. #### Deprecations (removal in next major release) - [#10839](https://github.com/pytest-dev/pytest/issues/10839): Requesting an asynchronous fixture without a \[pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or `autouse=True`. For guidance on how to work around this warning see `sync-test-async-fixture`{.interpreted-text role="ref"}. #### New features - [#11538](https://github.com/pytest-dev/pytest/issues/11538): Added `pytest.RaisesGroup`{.interpreted-text role="class"} as an equivalent to `pytest.raises`{.interpreted-text role="func"} for expecting `ExceptionGroup`{.interpreted-text role="exc"}. Also adds `pytest.RaisesExc`{.interpreted-text role="class"} which is now the logic behind `pytest.raises`{.interpreted-text role="func"} and used as parameter to `pytest.RaisesGroup`{.interpreted-text role="class"}. `RaisesGroup` includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating `except* <except_star>`{.interpreted-text role="ref"}. See `assert-matching-exception-groups`{.interpreted-text role="ref"} and docstrings for more information. - [#12081](https://github.com/pytest-dev/pytest/issues/12081): Added `capteesys`{.interpreted-text role="fixture"} to capture AND pass output to next handler set by `--capture=`. - [#12504](https://github.com/pytest-dev/pytest/issues/12504): `pytest.mark.xfail`{.interpreted-text role="func"} now accepts `pytest.RaisesGroup`{.interpreted-text role="class"} for the `raises` parameter when you expect an exception group. You can also pass a `pytest.RaisesExc`{.interpreted-text role="class"} if you e.g. want to make use of the `check` parameter. - [#12713](https://github.com/pytest-dev/pytest/issues/12713): New \[--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level. This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose. - [#12749](https://github.com/pytest-dev/pytest/issues/12749): pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file. For example: ```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]{.title-ref} from \[tests/test_testament.py]{.title-ref} because it starts with \[Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace. This behavior can now be prevented by setting the new `collect_imported_tests`{.interpreted-text role="confval"} configuration option to `false`, which will make pytest collect classes/functions from test files **only** if they are defined in that file. \-- by `FreerGit`{.interpreted-text role="user"} - [#12765](https://github.com/pytest-dev/pytest/issues/12765): Thresholds to trigger snippet truncation can now be set with `truncation_limit_lines`{.interpreted-text role="confval"} and `truncation_limit_chars`{.interpreted-text role="confval"}. See `truncation-params`{.interpreted-text role="ref"} for more information. - [#13125](https://github.com/pytest-dev/pytest/issues/13125): `console_output_style`{.interpreted-text role="confval"} now supports `times` to show execution time of each test. - [#13192](https://github.com/pytest-dev/pytest/issues/13192): `pytest.raises`{.interpreted-text role="func"} will now raise a warning when passing an empty string to `match`, as this will match against any value. Use `match="^$"` if you want to check that an exception has no message. - [#13192](https://github.com/pytest-dev/pytest/issues/13192): `pytest.raises`{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has `^` and `$` and is otherwise escaped. - [#13192](https://github.com/pytest-dev/pytest/issues/13192): You can now pass `with pytest.raises(check=fn): <pytest.raises>`{.interpreted-text role="func"}, where `fn` is a function which takes a raised exception and returns a boolean. The `raises` fails if no exception was raised (as usual), passes if an exception is raised and `fn` returns `True` (as well as `match` and the type matching, if specified, which are checked before), and propagates the exception if `fn` returns `False` (which likely also fails the test). - [#13228](https://github.com/pytest-dev/pytest/issues/13228): `hidden-param`{.interpreted-text role="ref"} can now be used in `id` of `pytest.param`{.interpreted-text role="func"} or in `ids` of `Metafunc.parametrize <pytest.Metafunc.parametrize>`{.interpreted-text role="py:func"}. It hides the parameter set from the test name. - [#13253](https://github.com/pytest-dev/pytest/issues/13253): New flag: `--disable-plugin-autoload <disable_plugin_autoload>`{.interpreted-text role="ref"} which works as an alternative to `PYTEST_DISABLE_PLUGIN_AUTOLOAD`{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files with `addopts`{.interpreted-text role="confval"}. #### Improvements in existing functionality - [#10224](https://github.com/pytest-dev/pytest/issues/10224): pytest's `short` and `long` traceback styles (`how-to-modifying-python-tb-printing`{.interpreted-text role="ref"}) now have partial `657`{.interpreted-text role="pep"} support and will show specific code segments in the traceback. ```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: 'NoneType' object has no attribute 'x' ``` \-- by `ammaraskar`{.interpreted-text role="user"} - [#11118](https://github.com/pytest-dev/pytest/issues/11118): Now `pythonpath`{.interpreted-text role="confval"} configures \[$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the \[-p]{.title-ref} command-line option. \-- by `millerdev`{.interpreted-text role="user"} - [#11381](https://github.com/pytest-dev/pytest/issues/11381): The `type` parameter of the `parser.addini` method now accepts \["int"]{.title-ref} and `"float"` parameters, facilitating the parsing of configuration values in the configuration file. Example: ```python def pytest_addoption(parser): parser.addini("int_value", type="int", default=2, help="my int value") parser.addini("float_value", type="float", default=4.2, help="my float value") ``` The \[pytest.ini]{.title-ref} file: ```ini [pytest] int_value = 3 float_value = 5.4 ``` - [#11525](https://github.com/pytest-dev/pytest/issues/11525): Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function. \-- by `the-compiler`{.interpreted-text role="user"} and `glyphack`{.interpreted-text role="user"} - [#12426](https://github.com/pytest-dev/pytest/issues/12426): A warning is now issued when `pytest.mark.usefixtures ref`{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored. - [#12707](https://github.com/pytest-dev/pytest/issues/12707): Exception chains can be navigated when dropped into Pdb in Python 3.13+. - [#12736](https://github.com/pytest-dev/pytest/issues/12736): Added a new attribute \[name]{.title-ref} with the fixed value \["pytest tests"]{.title-ref} to the root tag \[testsuites]{.title-ref} of the junit-xml generated by pytest. This attribute is part of many junit-xml specifications and is even part of the \[junit-10.xsd]{.title-ref} specification that pytest's implementation is based on. - [#12943](https://github.com/pytest-dev/pytest/issues/12943): If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info. - [#12958](https://github.com/pytest-dev/pytest/issues/12958): A number of `unraisable <unraisable>`{.interpreted-text role="ref"} enhancements: - Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions. - Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions. - Collect multiple unraisable exceptions per test phase. - Report the `tracemalloc`{.interpreted-text role="mod"} allocation traceback (if available). - Avoid using a generator based hook to allow handling `StopIteration`{.interpreted-text role="class"} in test failures. - Report the unraisable exception as the cause of the `pytest.PytestUnraisableExceptionWarning`{.interpreted-text role="class"} exception if raised. - Compute the `repr` of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object. - [#13010](https://github.com/pytest-dev/pytest/issues/13010): `pytest.approx`{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed. - [#13016](https://github.com/pytest-dev/pytest/issues/13016): A number of `threadexception <unraisable>`{.interpreted-text role="ref"} enhancements: - Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads. - Collect multiple thread exceptions per test phase. - Report the `tracemalloc`{.interpreted-text role="mod"} allocation traceback (if available). - Avoid using a generator based hook to allow handling `StopIteration`{.interpreted-text role="class"} in test failures. - Report the thread exception as the cause of the `pytest.PytestUnhandledThreadExceptionWarning`{.interpreted-text role="class"} exception if raised. - Extract the `name` of the thread object in the excepthook which should help with resurrection of the thread. - [#13031](https://github.com/pytest-dev/pytest/issues/13031): An empty parameter set as in `pytest.mark.parametrize([], ids=idfunc)` will no longer trigger a call to `idfunc` with internal objects. - [#13115](https://github.com/pytest-dev/pytest/issues/13115): Allows supplying `ExceptionGroup[Exception]` and `BaseExceptionGroup[BaseException]` to `pytest.raises` to keep full typing on `ExceptionInfo <pytest.ExceptionInfo>`{.interpreted-text role="class"}: ```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](https://github.com/pytest-dev/pytest/issues/13122): The `--stepwise` mode received a number of improvements: - It no longer forgets the last failed test in case pytest is executed later without the flag. This enables the following workflow: 1. Execute pytest with `--stepwise`, pytest then stops at the first failing test; 2. Iteratively update the code and run the test in isolation, without the `--stepwise` flag (for example in an IDE), until it is fixed. 3. Execute pytest with `--stepwise` again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests. Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test. This change however might cause issues if the `--stepwise` mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future). - New `--stepwise-reset`/`--sw-reset` flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning. - [#13308](https://github.com/pytest-dev/pytest/issues/13308): Added official support for Python 3.14. - [#13380](https://github.com/pytest-dev/pytest/issues/13380): Fix `ExceptionGroup`{.interpreted-text role="class"} traceback filtering to exclude pytest internals. - [#13415](https://github.com/pytest-dev/pytest/issues/13415): The author metadata of the BibTex example is now correctly formatted with last names following first names. An example of BibLaTex has been added. BibTex and BibLaTex examples now clearly indicate that what is cited is software. \-- by `willynilly`{.interpreted-text role="user"} - [#13420](https://github.com/pytest-dev/pytest/issues/13420): Improved test collection performance by optimizing path resolution used in `FSCollector`. - [#13457](https://github.com/pytest-dev/pytest/issues/13457): The error message about duplicate parametrization no longer displays an internal stack trace. - [#4112](https://github.com/pytest-dev/pytest/issues/4112): Using `pytest.mark.usefixtures <pytest.mark.usefixtures ref>`{.interpreted-text role="ref"} on `pytest.param`{.interpreted-text role="func"} now produces an error instead of silently doing nothing. - [#5473](https://github.com/pytest-dev/pytest/issues/5473): Replace \[:]{.title-ref} with \[;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling `pytest.main`{.interpreted-text role="func"}. - ``` [#6985](https://github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000. ``` ```` : - The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results. - Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 ± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 ± 1]{.title-ref}). Example: **Previous Output:** ``` console >>> pytest.approx(42, abs=1) 42 ± 1.0e+00 ``` **Current Output:** ``` console >>> pytest.approx(42, abs=1) 42 ± 1 ``` \-- by `fazeelghafoor`{.interpreted-text role="user"} ```` - [#7683](https://github.com/pytest-dev/pytest/issues/7683): The formerly optional `pygments` dependency is now required, causing output always to be source-highlighted (unless disabled via the `--code-highlight=no` CLI option). #### Bug fixes - [#10404](https://github.com/pytest-dev/pytest/issues/10404): Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible so that warnings as errors are collected throughout the pytest run and before the unraisable and threadexcept hooks are removed. This allows very late warnings and unraisable/threadexcept exceptions to fail the test suite. This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered. - [#11067](https://github.com/pytest-dev/pytest/issues/11067): The test report is now consistent regardless if the test xfailed via `pytest.mark.xfail <pytest.mark.xfail ref>`{.interpreted-text role="ref"} or `pytest.fail`{.interpreted-text role="func"}. Previously, *xfailed* tests via the marker would have the string `"reason: "` prefixed to the message, while those *xfailed* via the function did not. The prefix has been removed. - [#12008](https://github.com/pytest-dev/pytest/issues/12008): In `11220`{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted. - [#12863](https://github.com/pytest-dev/pytest/issues/12863): Fix applying markers, including `pytest.mark.parametrize <pytest.mark.parametrize ref>`{.interpreted-text role="ref"} when placed above \[[@staticmethod](https://github.com/staticmethod)]{.title-ref} or \[[@classmethod](https://github.com/classmethod)]{.title-ref}. - [#12929](https://github.com/pytest-dev/pytest/issues/12929): Handle StopIteration from test cases, setup and teardown correctly. - [#12938](https://github.com/pytest-dev/pytest/issues/12938): Fixed `--durations-min` argument not respected if `-vv` is used. - [#12946](https://github.com/pytest-dev/pytest/issues/12946): Fixed missing help for `pdb`{.interpreted-text role="mod"} commands wrapped by pytest -- by `adamchainz`{.interpreted-text role="user"}. - [#12981](https://github.com/pytest-dev/pytest/issues/12981): Prevent exceptions in `pytest.Config.add_cleanup`{.interpreted-text role="func"} callbacks preventing further cleanups. - [#13047](https://github.com/pytest-dev/pytest/issues/13047): Restore `pytest.approx`{.interpreted-text role="func"} handling of equality checks between \[bool]{.title-ref} and \[numpy.bool\_]{.title-ref} types. Comparing \[bool]{.title-ref} and \[numpy.bool\_]{.title-ref} using `pytest.approx`{.interpreted-text role="func"} accidentally changed in version \[8.3.4]{.title-ref} and \[8.3.5]{.title-ref} to no longer match: ```pycon >>> import numpy as np >>> from pytest import approx >>> [np.True_, np.True_] == pytest.approx([True, True]) False ``` This has now been fixed: ```pycon >>> [np.True_, np.True_] == pytest.approx([True, True]) True ``` - [#13119](https://github.com/pytest-dev/pytest/issues/13119): Improved handling of invalid regex patterns for filter warnings by providing a clear error message. - [#13175](https://github.com/pytest-dev/pytest/issues/13175): The diff is now also highlighted correctly when comparing two strings. - [#13248](https://github.com/pytest-dev/pytest/issues/13248): Fixed an issue where passing a `scope` in `Metafunc.parametrize <pytest.Metafunc.parametrize>`{.interpreted-text role="py:func"} with `indirect=True` could result in other fixtures being unable to depend on the parametrized fixture. - [#13291](https://github.com/pytest-dev/pytest/issues/13291): Fixed `repr` of `attrs` objects in assertion failure messages when using `attrs>=25.2`. - [#13312](https://github.com/pytest-dev/pytest/issues/13312): Fixed a possible `KeyError` crash on PyPy during collection of tests involving higher-scoped parameters. - [#13345](https://github.com/pytest-dev/pytest/issues/13345): Fix type hints for `pytest.TestReport.when`{.interpreted-text role="attr"} and `pytest.TestReport.location`{.interpreted-text role="attr"}. - [#13377](https://github.com/pytest-dev/pytest/issues/13377): Fixed handling of test methods with positional-only parameter syntax. Now, methods are supported that formally define `self` as positional-only and/or fixture parameters as keyword-only, e.g.: ```python class TestClass: def test_method(self, /, *, fixture): ... ``` Before, this caused an internal error in pytest. - [#13384](https://github.com/pytest-dev/pytest/issues/13384): Fixed an issue where pytest could report negative durations. - [#13420](https://github.com/pytest-dev/pytest/issues/13420): Added `lru_cache` to `nodes._check_initialpaths_for_relpath`. - [#9037](https://github.com/pytest-dev/pytest/issues/9037): Honor `disable_test_id_escaping_and_forfeit_all_rights_to_community_support`{.interpreted-text role="confval"} when escaping ids in parametrized tests. #### Improved documentation - [#12535](https://github.com/pytest-dev/pytest/issues/12535): \[This example]{.title-ref}<<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures>> showed `print` statements that do not exactly reflect what the different branches actually do. The fix makes the example more precise. - [#13218](https://github.com/pytest-dev/pytest/issues/13218): Pointed out in the `pytest.approx`{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one. - [#13221](https://github.com/pytest-dev/pytest/issues/13221): Improved grouping of CLI options in the `--help` output. - [#6649](https://github.com/pytest-dev/pytest/issues/6649): Added `~pytest.TerminalReporter`{.interpreted-text role="class"} to the `api-reference`{.interpreted-text role="ref"} documentation page. - [#8612](https://github.com/pytest-dev/pytest/issues/8612): Add a recipe for handling abstract test classes in the documentation. A new example has been added to the documentation to demonstrate how to use a mixin class to handle abstract test classes without manually setting the `__test__` attribute for subclasses. This ensures that subclasses of abstract test classes are automatically collected by pytest. #### Packaging updates and notes for downstreams - [#13317](https://github.com/pytest-dev/pytest/issues/13317): Specified minimum allowed versions of `colorama`, `iniconfig`, and `packaging`; and bumped the minimum allowed version of `exceptiongroup` for `python_version<'3.11'` from a release candidate to a full release. #### Contributor-facing changes - [#12017](https://github.com/pytest-dev/pytest/issues/12017): Mixed internal improvements: - Migrate formatting to f-strings in some tests. - Use type-safe constructs in JUnitXML tests. - Moved`MockTiming` into `_pytest.timing`. \-- by `RonnyPfannschmidt`{.interpreted-text role="user"} - [#12647](https://github.com/pytest-dev/pytest/issues/12647): Fixed running the test suite with the `hypothesis` pytest plugin. #### Miscellaneous internal changes - [#6649](https://github.com/pytest-dev/pytest/issues/6649): Added `~pytest.TerminalReporter`{.interpreted-text role="class"} to the public pytest API, as it is part of the signature of the `pytest_terminal_summary`{.interpreted-text role="hook"} hook. ### [`v8.3.5`](https://github.com/pytest-dev/pytest/releases/tag/8.3.5) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.3.4...8.3.5) ### pytest 8.3.5 (2025-03-02) #### Bug fixes - [#11777](https://github.com/pytest-dev/pytest/issues/11777): Fixed issue where sequences were still being shortened even with `-vv` verbosity. - [#12888](https://github.com/pytest-dev/pytest/issues/12888): 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](https://github.com/pytest-dev/pytest/issues/13026): Fixed `AttributeError`{.interpreted-text role="class"} crash when using `--import-mode=importlib` when top-level directory same name as another module of the standard library. - [#13053](https://github.com/pytest-dev/pytest/issues/13053): 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](https://github.com/pytest-dev/pytest/issues/13083): Fixed issue where pytest could crash if one of the collected directories got removed during collection. #### Improved documentation - [#12842](https://github.com/pytest-dev/pytest/issues/12842): Added dedicated page about using types with pytest. See `types`{.interpreted-text role="ref"} for detailed usage. #### Contributor-facing changes - [#13112](https://github.com/pytest-dev/pytest/issues/13112): Fixed selftest failures in `test_terminal.py` with Pygments >= 2.19.0 - [#13256](https://github.com/pytest-dev/pytest/issues/13256): Support for Towncrier versions released in 2024 has been re-enabled when building Sphinx docs -- by `webknjaz`{.interpreted-text role="user"}. ### [`v8.3.4`](https://github.com/pytest-dev/pytest/releases/tag/8.3.4) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.3.3...8.3.4) ### pytest 8.3.4 (2024-12-01) #### Bug fixes - [#12592](https://github.com/pytest-dev/pytest/issues/12592): Fixed `KeyError`{.interpreted-text role="class"} crash when using `--import-mode=importlib` in a directory layout where a directory contains a child directory with the same name. - [#12818](https://github.com/pytest-dev/pytest/issues/12818): Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the `AST`, like [executing](https://github.com/alexmojaki/executing). - [#12849](https://github.com/pytest-dev/pytest/issues/12849): ANSI escape codes for colored output now handled correctly in `pytest.fail`{.interpreted-text role="func"} with \[pytrace=False]{.title-ref}. - [#9353](https://github.com/pytest-dev/pytest/issues/9353): `pytest.approx`{.interpreted-text role="func"} now uses strict equality when given booleans. #### Improved documentation - [#10558](https://github.com/pytest-dev/pytest/issues/10558): Fix ambiguous docstring of `pytest.Config.getoption`{.interpreted-text role="func"}. - [#10829](https://github.com/pytest-dev/pytest/issues/10829): Improve documentation on the current handling of the `--basetemp` option and its lack of retention functionality (`temporary directory location and retention`{.interpreted-text role="ref"}). - [#12866](https://github.com/pytest-dev/pytest/issues/12866): Improved cross-references concerning the `recwarn`{.interpreted-text role="fixture"} fixture. - [#12966](https://github.com/pytest-dev/pytest/issues/12966): Clarify `filterwarnings`{.interpreted-text role="ref"} docs on filter precedence/order when using multiple `@pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>`{.interpreted-text role="ref"} marks. #### Contributor-facing changes - [#12497](https://github.com/pytest-dev/pytest/issues/12497): Fixed two failing pdb-related tests on Python 3.13. ### [`v8.3.3`](https://github.com/pytest-dev/pytest/releases/tag/8.3.3) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.3.2...8.3.3) # pytest 8.3.3 (2024-09-09) ## Bug fixes - [#12446](https://github.com/pytest-dev/pytest/issues/12446): Avoid calling `@property` (and other instance descriptors) during fixture discovery -- by `asottile`{.interpreted-text role="user"} - [#12659](https://github.com/pytest-dev/pytest/issues/12659): Fixed the issue of not displaying assertion failure differences when using the parameter `--import-mode=importlib` in pytest>=8.1. - [#12667](https://github.com/pytest-dev/pytest/issues/12667): Fixed a regression where type change in \[ExceptionInfo.errisinstance]{.title-ref} caused \[mypy]{.title-ref} to fail. - [#12744](https://github.com/pytest-dev/pytest/issues/12744): Fixed typing compatibility with Python 3.9 or less -- replaced \[typing.Self]{.title-ref} with \[typing_extensions.Self]{.title-ref} -- by `Avasam`{.interpreted-text role="user"} - [#12745](https://github.com/pytest-dev/pytest/issues/12745): Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments. - [#6682](https://github.com/pytest-dev/pytest/issues/6682): Fixed bug where the verbosity levels where not being respected when printing the "msg" part of failed assertion (as in `assert condition, msg`). - [#9422](https://github.com/pytest-dev/pytest/issues/9422): Fix bug where disabling the terminal plugin via `-p no:terminal` would cause crashes related to missing the `verbose` option. \-- by `GTowers1`{.interpreted-text role="user"} ## Improved documentation - [#12663](https://github.com/pytest-dev/pytest/issues/12663): Clarify that the \[pytest_deselected]{.title-ref} hook should be called from \[pytest_collection_modifyitems]{.title-ref} hook implementations when items are deselected. - [#12678](https://github.com/pytest-dev/pytest/issues/12678): Remove erroneous quotes from \[tmp_path_retention_policy]{.title-ref} example in docs. ## Miscellaneous internal changes - [#12769](https://github.com/pytest-dev/pytest/issues/12769): Fix typos discovered by codespell and add codespell to pre-commit hooks. ### [`v8.3.2`](https://github.com/pytest-dev/pytest/releases/tag/8.3.2) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.3.1...8.3.2) # pytest 8.3.2 (2024-07-24) ## Bug fixes - [#12652](https://github.com/pytest-dev/pytest/issues/12652): Resolve regression \[conda]{.title-ref} environments where no longer being automatically detected. \-- by `RonnyPfannschmidt`{.interpreted-text role="user"} ### [`v8.3.1`](https://github.com/pytest-dev/pytest/releases/tag/8.3.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.3.0...8.3.1) # pytest 8.3.1 (2024-07-20) 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. ### [`v8.3.0`](https://github.com/pytest-dev/pytest/releases/tag/8.3.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.2.2...8.3.0) ### pytest 8.3.0 (2024-07-20) #### New features - [#12231](https://github.com/pytest-dev/pytest/issues/12231): Added \[--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results. - If the \[--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown. - The style of traceback for XFAIL is set with \[--tb]{.title-ref}, and can be \[auto|long|short|line|native|no]{.title-ref}. - Note: Even if you have \[--xfail-tb]{.title-ref} set, you won't see them if \[--tb=no]{.title-ref}. Some history: With pytest 8.0, \[-rx]{.title-ref} or \[-ra]{.title-ref} 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't want to see all of the xfail tracebacks. This change detaches xfail tracebacks from \[-rx]{.title-ref}, and now we turn on xfail tracebacks with \[--xfail-tb]{.title-ref}. With this, the default \[-rx]{.title-ref}/ \[-ra]{.title-ref} 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. - [#12281](https://github.com/pytest-dev/pytest/issues/12281): Added support for keyword matching in marker expressions. Now tests can be selected by marker keyword arguments. Supported values are `int`{.interpreted-text role="class"}, (unescaped) `str`{.interpreted-text role="class"}, `bool`{.interpreted-text role="class"} & `None`{.interpreted-text role="data"}. See `marker examples <marker_keyword_expression_example>`{.interpreted-text role="ref"} for more information. \-- by `lovetheguitar`{.interpreted-text role="user"} - [#12567](https://github.com/pytest-dev/pytest/issues/12567): 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 `pbrezina`{.interpreted-text role="user"} #### Improvements in existing functionality - [#12469](https://github.com/pytest-dev/pytest/issues/12469): The console output now uses the "third-party plugins" terminology, replacing the previously established but confusing and outdated reference to `setuptools <setuptools:index>`{.interpreted-text role="std:doc"} \-- by `webknjaz`{.interpreted-text role="user"}. - [#12544](https://github.com/pytest-dev/pytest/issues/12544), [#12545](https://github.com/pytest-dev/pytest/issues/12545): Python virtual environment detection was improved by checking for a `pyvenv.cfg`{.interpreted-text role="file"} file, ensuring reliable detection on various platforms -- by `zachsnickers`{.interpreted-text role="user"}. - [#2871](https://github.com/pytest-dev/pytest/issues/2871): Do not truncate arguments to functions in output when running with \[-vvv]{.title-ref}. - [#389](https://github.com/pytest-dev/pytest/issues/389): The readability of assertion introspection of bound methods has been enhanced \-- by `farbodahm`{.interpreted-text role="user"}, `webknjaz`{.interpreted-text role="user"}, `obestwalter`{.interpreted-text role="user"}, `flub`{.interpreted-text role="user"} and `glyphack`{.interpreted-text role="user"}. Earlier, it was like: ```console =================================== FAILURES =================================== _____________________________________ test _____________________________________ def test(): > assert Help().fun() == 2 E assert 1 == 2 E + where 1 = <bound method Help.fun of <example.Help instance at 0x256a830>>() E + where <bound method Help.fun of <example.Help instance at 0x256a830>> = <example.Help instance at 0x256a830>.fun E + where <example.Help instance at 0x256a830> = Help() example.py:7: AssertionError =========================== 1 failed in 0.03 seconds =========================== ``` And now it's like: ```console =================================== FAILURES =================================== _____________________________________ test _____________________________________ def test(): > assert Help().fun() == 2 E assert 1 == 2 E + where 1 = fun() E + where fun = <test_local.Help object at 0x1074be230>.fun E + where <test_local.Help object at 0x1074be230> = Help() test_local.py:13: AssertionError =========================== 1 failed in 0.03 seconds =========================== ``` - [#7662](https://github.com/pytest-dev/pytest/issues/7662): Added timezone information to the testsuite timestamp in the JUnit XML report. #### Bug fixes - [#11706](https://github.com/pytest-dev/pytest/issues/11706): Fixed reporting of teardown errors in higher-scoped fixtures when using \[--maxfail]{.title-ref} or \[--stepwise]{.title-ref}. 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](https://github.com/pytest-dev/pytest/issues/11797): `pytest.approx`{.interpreted-text role="func"} now correctly handles `Sequence <collections.abc.Sequence>`{.interpreted-text role="class"}-like objects. - [#12204](https://github.com/pytest-dev/pytest/issues/12204), [#12264](https://github.com/pytest-dev/pytest/issues/12264): 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 `bluetech`{.interpreted-text role="user"}. 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](https://github.com/pytest-dev/pytest/issues/12275): Fixed collection error upon encountering an `abstract <abc>`{.interpreted-text role="mod"} class, including abstract \[unittest.TestCase]{.title-ref} subclasses. - [#12328](https://github.com/pytest-dev/pytest/issues/12328): 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](https://github.com/pytest-dev/pytest/issues/12424): Fixed crash with \[assert testcase is not None]{.title-ref} assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2. - [#12472](https://github.com/pytest-dev/pytest/issues/12472): Fixed a crash when returning category `"error"` or `"failed"` with a custom test status from `pytest_report_teststatus`{.interpreted-text role="hook"} hook -- `pbrezina`{.interpreted-text role="user"}. - [#12505](https://github.com/pytest-dev/pytest/issues/12505): Improved handling of invalid regex patterns in `pytest.raises(match=r'...') <pytest.raises>`{.interpreted-text role="func"} by providing a clear error message. - [#12580](https://github.com/pytest-dev/pytest/issues/12580): Fixed a crash when using the cache class on Windows and the cache directory was created concurrently. - [#6962](https://github.com/pytest-dev/pytest/issues/6962): Parametrization parameters are now compared using \[==]{.title-ref} instead of \[is]{.title-ref} (\[is]{.title-ref} is still used as a fallback if the parameter does not support \[==]{.title-ref}). This fixes use of parameters such as lists, which have a different \[id]{.title-ref} but compare equal, causing fixtures to be re-computed instead of being cached. - [#7166](https://github.com/pytest-dev/pytest/issues/7166): Fixed progress percentages (the `[ 87%]` at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist `-n`. #### Improved documentation - [#12153](https://github.com/pytest-dev/pytest/issues/12153): Documented using `PYTEST_VERSION`{.interpreted-text role="envvar"} to detect if code is running from within a pytest run. - [#12469](https://github.com/pytest-dev/pytest/issues/12469): The external plugin mentions in the documentation now avoid mentioning `setuptools entry-points <setuptools:index>`{.interpreted-text role="std:doc"} as the concept is much more generic nowadays. Instead, the terminology of "external", "installed", or "third-party" plugins (or packages) replaces that. \-- by `webknjaz`{.interpreted-text role="user"} - [#12577](https://github.com/pytest-dev/pytest/issues/12577): \[CI]{.title-ref} and \[BUILD_NUMBER]{.title-ref} environment variables role is discribed in the reference doc. They now also appear when doing \[pytest -h]{.title-ref} \-- by `MarcBresson`{.interpreted-text role="user"}. #### Contributor-facing changes - [#12467](https://github.com/pytest-dev/pytest/issues/12467): Migrated all internal type-annotations to the python3.10+ style by using the \[annotations]{.title-ref} future import. \-- by `RonnyPfannschmidt`{.interpreted-text role="user"} - [#11771](https://github.com/pytest-dev/pytest/issues/11771), [#12557](https://github.com/pytest-dev/pytest/issues/12557): 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 `x612skm`{.interpreted-text role="user"} - [#12493](https://github.com/pytest-dev/pytest/issues/12493): 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 `doc/en/_changelog_towncrier_draft.rst`{.interpreted-text role="file"}. 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: ```console $ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst ``` \-- by `webknjaz`{.interpreted-text role="user"} - [#12498](https://github.com/pytest-dev/pytest/issues/12498): All the undocumented `tox` environments now have descriptions. They can be listed in one's development environment by invoking `tox -av` in a terminal. \-- by `webknjaz`{.interpreted-text role="user"} - [#12501](https://github.com/pytest-dev/pytest/issues/12501): 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 `webknjaz`{.interpreted-text role="user"} - [#12502](https://github.com/pytest-dev/pytest/issues/12502): The UX of the GitHub automation making pull requests to update the plugin list has been updated. Previously, the maintainers had to close the automatically created pull requests and re-open them to trigger the CI runs. From now on, they only need to click the \[Ready for review]{.title-ref} button instead. \-- by `webknjaz`{.interpreted-text role="user"} - [#12522](https://github.com/pytest-dev/pytest/issues/12522): The `:pull:` RST role has been replaced with a shorter `:pr:` due to starting to use the implementation from the third-party `sphinx-issues`{.interpreted-text role="pypi"} Sphinx extension \-- by `webknjaz`{.interpreted-text role="user"}. - [#12531](https://github.com/pytest-dev/pytest/issues/12531): The coverage reporting configuration has been updated to exclude pytest's own tests marked as expected to fail from the coverage report. This has an effect of reducing the influence of flaky tests on the resulting number. \-- by `webknjaz`{.interpreted-text role="user"} - [#12533](https://github.com/pytest-dev/pytest/issues/12533): The `extlinks` Sphinx extension is no longer enabled. The `:bpo:` role it used to declare has been removed with that. BPO itself has migrated to GitHub some years ago and it is possible to link the respective issues by using their GitHub issue numbers and the `:issue:` role that the `sphinx-issues` extension implements. \-- by `webknjaz`{.interpreted-text role="user"} - [#12562](https://github.com/pytest-dev/pytest/issues/12562): Possible typos in using the `:user:` RST role is now being linted through the pre-commit tool integration -- by `webknjaz`{.interpreted-text role="user"}. ### [`v8.2.2`](https://github.com/pytest-dev/pytest/releases/tag/8.2.2) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.2.1...8.2.2) # pytest 8.2.2 (2024-06-04) ## Bug Fixes - [#12355](https://github.com/pytest-dev/pytest/issues/12355): Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters. - [#12367](https://github.com/pytest-dev/pytest/issues/12367): Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown. - [#12381](https://github.com/pytest-dev/pytest/issues/12381): Fix possible "Directory not empty" crashes arising from concurent cache dir (`.pytest_cache`) creation. Regressed in pytest 8.2.0. ## Improved Documentation - [#12290](https://github.com/pytest-dev/pytest/issues/12290): Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme. - [#12356](https://github.com/pytest-dev/pytest/issues/12356): Added a subsection to the documentation for debugging flaky tests to mention lack of thread safety in pytest as a possible source of flakyness. - [#12363](https://github.com/pytest-dev/pytest/issues/12363): The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results. ### [`v8.2.1`](https://github.com/pytest-dev/pytest/releases/tag/8.2.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.2.0...8.2.1) # pytest 8.2.1 (2024-05-19) ## Improvements - [#12334](https://github.com/pytest-dev/pytest/issues/12334): Support for Python 3.13 (beta1 at the time of writing). ## Bug Fixes - [#12120](https://github.com/pytest-dev/pytest/issues/12120): Fix \[PermissionError]{.title-ref} crashes arising from directories which are not selected on the command-line. - [#12191](https://github.com/pytest-dev/pytest/issues/12191): Keyboard interrupts and system exits are now properly handled during the test collection. - [#12300](https://github.com/pytest-dev/pytest/issues/12300): Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only. - [#12308](https://github.com/pytest-dev/pytest/issues/12308): Fix a regression in pytest 8.2.0 where the permissions of automatically-created `.pytest_cache` directories became `rwx------` instead of the expected `rwxr-xr-x`. ## Trivial/Internal Changes - [#12333](https://github.com/pytest-dev/pytest/issues/12333): pytest releases are now attested using the recent [Artifact Attestation](https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/) support from GitHub, allowing users to verify the provenance of pytest's sdist and wheel artifacts. ### [`v8.2.0`](https://github.com/pytest-dev/pytest/releases/tag/8.2.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.1.2...8.2.0) # pytest 8.2.0 (2024-04-27) ## Deprecations - [#12069](https://github.com/pytest-dev/pytest/issues/12069): A deprecation warning is now raised when implementations of one of the following hooks request a deprecated `py.path.local` parameter instead of the `pathlib.Path` parameter which replaced it: - `pytest_ignore_collect`{.interpreted-text role="hook"} - the `path` parameter - use `collection_path` instead. - `pytest_collect_file`{.interpreted-text role="hook"} - the `path` parameter - use `file_path` instead. - `pytest_pycollect_makemodule`{.interpreted-text role="hook"} - the `path` parameter - use `module_path` instead. - `pytest_report_header`{.interpreted-text role="hook"} - the `startdir` parameter - use `start_path` instead. - `pytest_report_collectionfinish`{.interpreted-text role="hook"} - the `startdir` parameter - use `start_path` instead. The replacement parameters are available since pytest 7.0.0. The old parameters will be removed in pytest 9.0.0. See `legacy-path-hooks-deprecated`{.interpreted-text role="ref"} for more details. ## Features - [#11871](https://github.com/pytest-dev/pytest/issues/11871): Added support for reading command line arguments from a file using the prefix character `@`, like e.g.: `pytest @tests.txt`. The file must have one argument per line. See `Read arguments from file <args-from-file>`{.interpreted-text role="ref"} for details. ## Improvements - [#11523](https://github.com/pytest-dev/pytest/issues/11523): `pytest.importorskip`{.interpreted-text role="func"} will now issue a warning if the module could be found, but raised `ImportError`{.interpreted-text role="class"} instead of `ModuleNotFoundError`{.interpreted-text role="class"}. The warning can be suppressed by passing `exc_type=ImportError` to `pytest.importorskip`{.interpreted-text role="func"}. See `import-or-skip-import-error`{.interpreted-text role="ref"} for details. - [#11728](https://github.com/pytest-dev/pytest/issues/11728): For `unittest`-based tests, exceptions during class cleanup (as raised by functions registered with `TestCase.addClassCleanup <unittest.TestCase.addClassCleanup>`{.interpreted-text role="meth"}) are now reported instead of silently failing. - [#11777](https://github.com/pytest-dev/pytest/issues/11777): Text is no longer truncated in the `short test summary info` section when `-vv` is given. - [#12112](https://github.com/pytest-dev/pytest/issues/12112): Improved namespace packages detection when `consider_namespace_packages`{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs). - [#9502](https://github.com/pytest-dev/pytest/issues/9502): Added `PYTEST_VERSION`{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value of `pytest.__version__`, and among other things can be used to easily check if code is running from within a pytest run. ## Bug Fixes - [#12065](https://github.com/pytest-dev/pytest/issues/12065): Fixed a regression in pytest 8.0.0 where test classes containing `setup_method` and tests using `@staticmethod` or `@classmethod` would crash with `AttributeError: 'NoneType' object has no attribute 'setup_method'`. Now the `request.instance <pytest.FixtureRequest.instance>`{.interpreted-text role="attr"} attribute of tests using `@staticmethod` and `@classmethod` is no longer `None`, but a fresh instance of the class, like in non-static methods. Previously it was `None`, and all fixtures of such tests would share a single `self`. - [#12135](https://github.com/pytest-dev/pytest/issues/12135): Fixed issue where fixtures adding their finalizer multiple times to fixtures they request would cause unreliable and non-intuitive teardown ordering in some instances. - [#12194](https://github.com/pytest-dev/pytest/issues/12194): Fixed a bug with `--importmode=importlib` and `--doctest-modules` where child modules did not appear as attributes in parent modules. - [#1489](https://github.com/pytest-dev/pytest/issues/1489): Fixed some instances where teardown of higher-scoped fixtures was not happening in the reverse order they were initialized in. ## Trivial/Internal Changes - [#12069](https://github.com/pytest-dev/pytest/issues/12069): `pluggy>=1.5.0` is now required. - [#12167](https://github.com/pytest-dev/pytest/issues/12167): `cache <cache>`{.interpreted-text role="ref"}: create supporting files (`CACHEDIR.TAG`, `.gitignore`, etc.) in a temporary directory to provide atomic semantics. ### [`v8.1.2`](https://github.com/pytest-dev/pytest/releases/tag/8.1.2) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.1.1...8.1.2) # pytest 8.1.2 (2024-04-26) ## Bug Fixes - [#12114](https://github.com/pytest-dev/pytest/issues/12114): Fixed error in `pytest.approx`{.interpreted-text role="func"} when used with \[numpy]{.title-ref} arrays and comparing with other types. ### [`v8.1.1`](https://github.com/pytest-dev/pytest/releases/tag/8.1.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.1.0...8.1.1) # pytest 8.1.1 (2024-03-08) ::: {.note} ::: {.title} Note ::: This release is not a usual bug fix release -- it contains features and improvements, being a follow up to `8.1.0`, which has been yanked from PyPI. ::: ## Features - [#11475](https://github.com/pytest-dev/pytest/issues/11475): Added the new `consider_namespace_packages`{.interpreted-text role="confval"} configuration option, defaulting to `False`. If set to `True`, pytest will attempt to identify modules that are part of [namespace packages](https://packaging.python.org/en/latest/guides/packaging-namespace-packages) when importing modules. - [#11653](https://github.com/pytest-dev/pytest/issues/11653): Added the new `verbosity_test_cases`{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity. See `Fine-grained verbosity <pytest.fine_grained_verbosity>`{.interpreted-text role="ref"} for more details. ## Improvements - [#10865](https://github.com/pytest-dev/pytest/issues/10865): `pytest.warns`{.interpreted-text role="func"} now validates that `warnings.warn`{.interpreted-text role="func"} was called with a \[str]{.title-ref} or a \[Warning]{.title-ref}. Currently in Python it is possible to use other types, however this causes an exception when `warnings.filterwarnings`{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](https://github.com/python/cpython/issues/103577) for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing. - [#11311](https://github.com/pytest-dev/pytest/issues/11311): When using `--override-ini` for paths in invocations without a configuration file defined, the current working directory is used as the relative directory. Previoulsy this would raise an `AssertionError`{.interpreted-text role="class"}. - [#11475](https://github.com/pytest-dev/pytest/issues/11475): `--import-mode=importlib <import-mode-importlib>`{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :py`sys.path`{.interpreted-text role="data"}), falling back to importing modules directly only if that fails. This means that installed packages will be imported under their canonical name if possible first, for example `app.core.models`, instead of having the module name always be derived from their path (for example `.env310.lib.site_packages.app.core.models`). - [#11801](https://github.com/pytest-dev/pytest/issues/11801): Added the `iter_parents() <_pytest.nodes.Node.iter_parents>`{.interpreted-text role="func"} helper method on nodes. It is similar to `listchain <_pytest.nodes.Node.listchain>`{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list. - [#11850](https://github.com/pytest-dev/pytest/issues/11850): Added support for `sys.last_exc`{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12. - [#11962](https://github.com/pytest-dev/pytest/issues/11962): In case no other suitable candidates for configuration file are found, a `pyproject.toml` (even without a `[tool.pytest.ini_options]` table) will be considered as the configuration file and define the `rootdir`. - [#11978](https://github.com/pytest-dev/pytest/issues/11978): Add `--log-file-mode` option to the logging plugin, enabling appending to log-files. This option accepts either `"w"` or `"a"` and defaults to `"w"`. Previously, the mode was hard-coded to be `"w"` which truncates the file before logging. - [#12047](https://github.com/pytest-dev/pytest/issues/12047): When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group. Previously, only the first exception was reported. ## Bug Fixes - [#11475](https://github.com/pytest-dev/pytest/issues/11475): Fixed regression where `--importmode=importlib` would import non-test modules more than once. - [#11904](https://github.com/pytest-dev/pytest/issues/11904): Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using `--pyargs`. This change improves the collection tree for tests specified using `--pyargs`, see `12043`{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8. - [#12011](https://github.com/pytest-dev/pytest/issues/12011): Fixed a regression in 8.0.1 whereby `setup_module` xunit-style fixtures are not executed when `--doctest-modules` is passed. - [#12014](https://github.com/pytest-dev/pytest/issues/12014): Fix the `stacklevel` used when warning about marks used on fixtures. - [#12039](https://github.com/pytest-dev/pytest/issues/12039): Fixed a regression in `8.0.2` where tests created using `tmp_path`{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows. ## Improved Documentation - [#11790](https://github.com/pytest-dev/pytest/issues/11790): Documented the retention of temporary directories created using the `tmp_path` fixture in more detail. ## Trivial/Internal Changes - [#11785](https://github.com/pytest-dev/pytest/issues/11785): Some changes were made to private functions which may affect plugins which access them: - `FixtureManager._getautousenames()` now takes a `Node` itself instead of the nodeid. - `FixtureManager.getfixturedefs()` now takes the `Node` itself instead of the nodeid. - The `_pytest.nodes.iterparentnodeids()` function is removed without replacement. Prefer to traverse the node hierarchy itself instead. If you really need to, copy the function from the previous pytest release. - [#12069](https://github.com/pytest-dev/pytest/issues/12069): Delayed the deprecation of the following features to `9.0.0`: - `node-ctor-fspath-deprecation`{.interpreted-text role="ref"}. - `legacy-path-hooks-deprecated`{.interpreted-text role="ref"}. It was discovered after `8.1.0` was released that the warnings about the impeding removal were not being displayed, so the team decided to revert the removal. This is the reason for `8.1.0` being yanked. # pytest 8.1.0 (YANKED) ::: {.note} ::: {.title} Note ::: This release has been **yanked**: it broke some plugins without the proper warning period, due to some warnings not showing up as expected. See [#12069](https://github.com/pytest-dev/pytest/issues/12069). ::: ### [`v8.1.0`](https://github.com/pytest-dev/pytest/releases/tag/8.1.0) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.0.2...8.1.0) # pytest 8.1.0 (YANKED) > \[!IMPORTANT]\ > This release has been **yanked**: it broke some plugins without the proper warning period, due to some warnings not showing up as expected. See [#12069](https://github.com/pytest-dev/pytest/issues/12069). ## Features - [#11475](https://github.com/pytest-dev/pytest/issues/11475): Added the new `consider_namespace_packages`{.interpreted-text role="confval"} configuration option, defaulting to `False`. If set to `True`, pytest will attempt to identify modules that are part of [namespace packages](https://packaging.python.org/en/latest/guides/packaging-namespace-packages) when importing modules. - [#11653](https://github.com/pytest-dev/pytest/issues/11653): Added the new `verbosity_test_cases`{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity. See `Fine-grained verbosity <pytest.fine_grained_verbosity>`{.interpreted-text role="ref"} for more details. ## Improvements - [#10865](https://github.com/pytest-dev/pytest/issues/10865): `pytest.warns`{.interpreted-text role="func"} now validates that `warnings.warn`{.interpreted-text role="func"} was called with a \[str]{.title-ref} or a \[Warning]{.title-ref}. Currently in Python it is possible to use other types, however this causes an exception when `warnings.filterwarnings`{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](https://github.com/python/cpython/issues/103577) for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing. - [#11311](https://github.com/pytest-dev/pytest/issues/11311): When using `--override-ini` for paths in invocations without a configuration file defined, the current working directory is used as the relative directory. Previoulsy this would raise an `AssertionError`{.interpreted-text role="class"}. - [#11475](https://github.com/pytest-dev/pytest/issues/11475): `--import-mode=importlib <import-mode-importlib>`{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :py`sys.path`{.interpreted-text role="data"}), falling back to importing modules directly only if that fails. This means that installed packages will be imported under their canonical name if possible first, for example `app.core.models`, instead of having the module name always be derived from their path (for example `.env310.lib.site_packages.app.core.models`). - [#11801](https://github.com/pytest-dev/pytest/issues/11801): Added the `iter_parents() <_pytest.nodes.Node.iter_parents>`{.interpreted-text role="func"} helper method on nodes. It is similar to `listchain <_pytest.nodes.Node.listchain>`{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list. - [#11850](https://github.com/pytest-dev/pytest/issues/11850): Added support for `sys.last_exc`{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12. - [#11962](https://github.com/pytest-dev/pytest/issues/11962): In case no other suitable candidates for configuration file are found, a `pyproject.toml` (even without a `[tool.pytest.ini_options]` table) will be considered as the configuration file and define the `rootdir`. - [#11978](https://github.com/pytest-dev/pytest/issues/11978): Add `--log-file-mode` option to the logging plugin, enabling appending to log-files. This option accepts either `"w"` or `"a"` and defaults to `"w"`. Previously, the mode was hard-coded to be `"w"` which truncates the file before logging. - [#12047](https://github.com/pytest-dev/pytest/issues/12047): When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group. Previously, only the first exception was reported. ## Bug Fixes - [#11904](https://github.com/pytest-dev/pytest/issues/11904): Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using `--pyargs`. This change improves the collection tree for tests specified using `--pyargs`, see `12043`{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8. - [#12011](https://github.com/pytest-dev/pytest/issues/12011): Fixed a regression in 8.0.1 whereby `setup_module` xunit-style fixtures are not executed when `--doctest-modules` is passed. - [#12014](https://github.com/pytest-dev/pytest/issues/12014): Fix the `stacklevel` used when warning about marks used on fixtures. - [#12039](https://github.com/pytest-dev/pytest/issues/12039): Fixed a regression in `8.0.2` where tests created using `tmp_path`{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows. ## Improved Documentation - [#11790](https://github.com/pytest-dev/pytest/issues/11790): Documented the retention of temporary directories created using the `tmp_path` fixture in more detail. ## Trivial/Internal Changes - [#11785](https://github.com/pytest-dev/pytest/issues/11785): Some changes were made to private functions which may affect plugins which access them: - `FixtureManager._getautousenames()` now takes a `Node` itself instead of the nodeid. - `FixtureManager.getfixturedefs()` now takes the `Node` itself instead of the nodeid. - The `_pytest.nodes.iterparentnodeids()` function is removed without replacement. Prefer to traverse the node hierarchy itself instead. If you really need to, copy the function from the previous pytest release. ### [`v8.0.2`](https://github.com/pytest-dev/pytest/releases/tag/8.0.2) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.0.1...8.0.2) # pytest 8.0.2 (2024-02-24) ## Bug Fixes - [#11895](https://github.com/pytest-dev/pytest/issues/11895): Fix collection on Windows where initial paths contain the short version of a path (for example `c:\PROGRA~1\tests`). - [#11953](https://github.com/pytest-dev/pytest/issues/11953): Fix an `IndexError` crash raising from `getstatementrange_ast`. - [#12021](https://github.com/pytest-dev/pytest/issues/12021): Reverted a fix to \[--maxfail]{.title-ref} handling in pytest 8.0.0 because it caused a regression in pytest-xdist whereby session fixture teardowns may get executed multiple times when the max-fails is reached. ### [`v8.0.1`](https://github.com/pytest-dev/pytest/releases/tag/8.0.1) [Compare Source](https://github.com/pytest-dev/pytest/compare/8.0.0...8.0.1) # pytest 8.0.1 (2024-02-16) ## Bug Fixes - [#11875](https://github.com/pytest-dev/pytest/issues/11875): Correctly handle errors from `getpass.getuser`{.interpreted-text role="func"} in Python 3.13. - [#11879](https://github.com/pytest-dev/pytest/issues/11879): Fix an edge case where `ExceptionInfo._stringify_exception` could crash `pytest.raises`{.interpreted-text role="func"}. - [#11906](https://github.com/pytest-dev/pytest/issues/11906): Fix regression with `pytest.warns`{.interpreted-text role="func"} using custom warning subclasses which have more than one parameter in their \[\_\_init\_\_]{.title-ref}. - [#11907](https://github.com/pytest-dev/pytest/issues/11907): Fix a regression in pytest 8.0.0 whereby calling `pytest.skip`{.interpreted-text role="func"} and similar control-flow exceptions within a `pytest.warns()`{.interpreted-text role="func"} block would get suppressed instead of propagating. - [#11929](https://github.com/pytest-dev/pytest/issues/11929): Fix a regression in pytest 8.0.0 whereby autouse fixtures defined in a module get ignored by the doctests in the module. - [#11937](https://github.com/pytest-dev/pytest/issues/11937): Fix a regression in pytest 8.0.0 whereby items would be collected in reverse order in some circumstances. ### [`v8.0.0`](https://github.com/pytest-dev/pytest/releases/tag/8.0.0): pytest 8.0.0 (2024-01-27) [Compare Source](https://github.com/pytest-dev/pytest/compare/7.4.4...8.0.0) See [8.0.0rc1](https://github.com/pytest-dev/pytest/releases/tag/8.0.0rc1) and [8.0.0rc2](https://github.com/pytest-dev/pytest/releases/tag/8.0.0rc2) for the full changes since pytest 7.4! #### Bug Fixes - [#11842](https://github.com/pytest-dev/pytest/issues/11842): Properly escape the `reason` of a `skip <pytest.mark.skip ref>`{.interpreted-text role="ref"} mark when writing JUnit XML files. - [#11861](https://github.com/pytest-dev/pytest/issues/11861): Avoid microsecond exceeds `1_000_000` when using `log-date-format` with `%f` specifier, which might cause the test suite to crash. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit

2026-10-29 15:10:19 -04:00

Update dependency pytest to v9 e646f2a332

BlazingNeutron closed this pull request

2026-10-30 08:40:57 -04:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

BlazingNeutron/wyoming-whisper-api-client!15

No description provided.

Rows
Columns