flask-wtform-tutorial
flask-wtform-tutorial copied to clipboard
Update dependency pytest to v8.4.1
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| pytest (changelog) | ==8.1.1 -> ==8.4.1 |
Release Notes
pytest-dev/pytest (pytest)
v8.4.1
pytest 8.4.1 (2025-06-17)
Bug fixes
-
#β13461: Corrected
_pytest.terminal.TerminalReporter.isattyto 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
faulthandlernot working on Windows.
v8.4.0
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 seesync-test-async-fixture{.interpreted-text role="ref"}.
New features
-
#β11538: Added
pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent topytest.raises{.interpreted-text role="func"} for expectingExceptionGroup{.interpreted-text role="exc"}. Also addspytest.RaisesExc{.interpreted-text role="class"} which is now the logic behindpytest.raises{.interpreted-text role="func"} and used as parameter topytest.RaisesGroup{.interpreted-text role="class"}.RaisesGroupincludes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulatingexcept* <except_star>{.interpreted-text role="ref"}. Seeassert-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 acceptspytest.RaisesGroup{.interpreted-text role="class"} for theraisesparameter when you expect an exception group. You can also pass apytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of thecheckparameter. -
#β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"} andtruncation_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 supportstimesto show execution time of each test. -
#β13192:
pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string tomatch, as this will match against any value. Usematch="^$"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"}, wherefnis a function which takes a raised exception and returns a boolean. Theraisesfails if no exception was raised (as usual), passes if an exception is raised andfnreturnsTrue(as well asmatchand the type matching, if specified, which are checked before), and propagates the exception iffnreturnsFalse(which likely also fails the test). -
#β13228:
hidden-param{.interpreted-text role="ref"} can now be used inidofpytest.param{.interpreted-text role="func"} or inidsofMetafunc.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 toPYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files withaddopts{.interpreted-text role="confval"}.
Improvements in existing functionality
-
#β10224: pytest's
shortandlongtraceback styles (how-to-modifying-python-tb-printing{.interpreted-text role="ref"}) now have partial657{.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
typeparameter of theparser.addinimethod 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"} andglyphack{.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
reprof 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
nameof 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 toidfuncwith internal objects. -
#β13115: Allows supplying
ExceptionGroup[Exception]andBaseExceptionGroup[BaseException]topytest.raisesto keep full typing onExceptionInfo <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
--stepwisemode 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:
- Execute pytest with
--stepwise, pytest then stops at the first failing test; - Iteratively update the code and run the test in isolation, without the
--stepwiseflag (for example in an IDE), until it is fixed. - Execute pytest with
--stepwiseagain 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
--stepwisemode 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). - Execute pytest with
-
New
--stepwise-reset/--sw-resetflag, 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"} onpytest.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"}.
[#​6985](https://redirect.github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.
: - The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.
- Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 Β± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 Β± 1]{.title-ref}).
Example:
**Previous Output:**
``` console
>>> pytest.approx(42, abs=1)
42 Β± 1.0e+00
```
**Current Output:**
``` console
>>> pytest.approx(42, abs=1)
42 Β± 1
```
\-- by `fazeelghafoor`{.interpreted-text role="user"}
- #β7683: The formerly optional
pygmentsdependency is now required, causing output always to be source-highlighted (unless disabled via the--code-highlight=noCLI 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"} orpytest.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-minargument not respected if-vvis used. -
#β12946: Fixed missing help for
pdb{.interpreted-text role="mod"} commands wrapped by pytest -- byadamchainz{.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]) FalseThis 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
scopeinMetafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"} withindirect=Truecould result in other fixtures being unable to depend on the parametrized fixture. -
#β13291: Fixed
reprofattrsobjects in assertion failure messages when usingattrs>=25.2. -
#β13312: Fixed a possible
KeyErrorcrash on PyPy during collection of tests involving higher-scoped parameters. -
#β13345: Fix type hints for
pytest.TestReport.when{.interpreted-text role="attr"} andpytest.TestReport.location{.interpreted-text role="attr"}. -
#β13377: Fixed handling of test methods with positional-only parameter syntax.
Now, methods are supported that formally define
selfas 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_cachetonodes._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
printstatements 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
--helpoutput. -
#β6649: Added
~pytest.TerminalReporter{.interpreted-text role="class"} to theapi-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, andpackaging; and bumped the minimum allowed version ofexceptiongroupforpython_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.
- Moved
MockTiminginto_pytest.timing.
-- by
RonnyPfannschmidt{.interpreted-text role="user"} -
#β12647: Fixed running the test suite with the
hypothesispytest 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 thepytest_terminal_summary{.interpreted-text role="hook"} hook.
v8.3.5
pytest 8.3.5 (2025-03-02)
Bug fixes
- #β11777: Fixed issue where sequences were still being shortened even with
-vvverbosity. - #β12888: Fixed broken input when using Python 3.13+ and a
libeditbuild of Python, such as on macOS or with uv-managed Python binaries from thepython-build-standaloneproject. This could manifest e.g. by a broken prompt when usingPdb, or seeing empty inputs with manual usage ofinput()and suspended capturing. - #β13026: Fixed
AttributeError{.interpreted-text role="class"} crash when using--import-mode=importlibwhen 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 anImportError - #β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.pywith 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
pytest 8.3.4 (2024-12-01)
Bug fixes
-
#β12592: Fixed
KeyError{.interpreted-text role="class"} crash when using--import-mode=importlibin 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
--basetempoption 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
pytest 8.3.3 (2024-09-09)
Bug fixes
-
#β12446: Avoid calling
@property(and other instance descriptors) during fixture discovery -- byasottile{.interpreted-text role="user"} -
#β12659: Fixed the issue of not displaying assertion failure differences when using the parameter
--import-mode=importlibin 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:terminalwould cause crashes related to missing theverboseoption.-- 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
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
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
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-skippedcommand 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"} -- bywebknjaz{.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 -- byzachsnickers{.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"} andglyphack{.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 handlesSequence <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 ofexc.SetupState.stackfailures are now a tuple(exc, tb)instead ofexc.
-
#β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 frompytest_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 atdoc/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
toxenvironments now have descriptions. They can be listed in one's development environment by invokingtox -avin 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
trivialchange log fragment type with an unclear and broad meaning. It was removed and we now havecontrib,miscandpackagingin 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-partysphinx-issues{.interpreted-text role="pypi"} Sphinx extension -- bywebknjaz{.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
extlinksSphinx 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 thesphinx-issuesextension 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 -- bywebknjaz{.interpreted-text role="user"}.
v8.2.2
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
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_cachedirectories becamerwx------instead of the expectedrwxr-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
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.localparameter instead of thepathlib.Pathparameter which replaced it:pytest_ignore_collect{.interpreted-text role="hook"} - thepathparameter - usecollection_pathinstead.pytest_collect_file{.interpreted-text role="hook"} - thepathparameter - usefile_pathinstead.pytest_pycollect_makemodule{.interpreted-text role="hook"} - thepathparameter - usemodule_pathinstead.pytest_report_header{.interpreted-text role="hook"} - thestartdirparameter - usestart_pathinstead.pytest_report_collectionfinish{.interpreted-text role="hook"} - thestartdirparameter - usestart_pathinstead.
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 raisedImportError{.interpreted-text role="class"} instead ofModuleNotFoundError{.interpreted-text role="class"}.The warning can be suppressed by passing
exc_type=ImportErrortopytest.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 withTestCase.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 infosection when-vvis 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 ofpytest.__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_methodand tests using@staticmethodor@classmethodwould crash withAttributeError: 'NoneType' object has no attribute 'setup_method'.Now the
request.instance <pytest.FixtureRequest.instance>{.interpreted-text role="attr"} attribute of tests using@staticmethodand@classmethodis no longerNone, but a fresh instance of the class, like in non-static methods. Previously it wasNone, and all fixtures of such tests would share a singleself. -
#β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=importliband--doctest-moduleswhere 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.0is 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
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.
Configuration
π Schedule: 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 was generated by Mend Renovate. View the repository job log.