Update dependency pytest to v8 - autoclosed #42
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^7.3.1
->^8.0.0
Release Notes
pytest-dev/pytest (pytest)
v8.0.2
Compare Source
pytest 8.0.2 (2024-02-24)
Bug Fixes
c:\PROGRA~1\tests
).IndexError
crash raising fromgetstatementrange_ast
.v8.0.1
Compare Source
pytest 8.0.1 (2024-02-16)
Bug Fixes
getpass.getuser
{.interpreted-text role="func"} in Python 3.13.ExceptionInfo._stringify_exception
could crashpytest.raises
{.interpreted-text role="func"}.pytest.warns
{.interpreted-text role="func"} using custom warning subclasses which have more than one parameter in their [__init__]{.title-ref}.pytest.skip
{.interpreted-text role="func"} and similar control-flow exceptions within apytest.warns()
{.interpreted-text role="func"} block would get suppressed instead of propagating.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
reason
of askip <pytest.mark.skip ref>
{.interpreted-text role="ref"} mark when writing JUnit XML files.1_000_000
when usinglog-date-format
with%f
specifier, which might cause the test suite to crash.v7.4.4
Compare Source
v7.4.3
: pytest 7.4.3 (2023-10-24)Compare Source
Bug Fixes
#10447: Markers are now considered in the reverse mro order to ensure base class markers are considered first -- this resolves a regression.
#11239: Fixed
:=
in asserts impacting unrelated test cases.#11439: Handled an edge case where :data:
sys.stderr
might already be closed when :ref:faulthandler
is tearing down.v7.4.2
: pytest 7.4.2 (2023-09-07)Compare Source
Bug Fixes
#11237: Fix doctest collection of
functools.cached_property
objects.#11306: Fixed bug using
--importmode=importlib
which would cause package__init__.py
files to be imported more than once in some cases.#11367: Fixed bug where
user_properties
where not being saved in the JUnit XML file if a fixture failed during teardown.#11394: Fixed crash when parsing long command line arguments that might be interpreted as files.
Improved Documentation
v7.4.1
: pytest 7.4.1 (2023-09-02)Compare Source
Bug Fixes
#10337: Fixed bug where fake intermediate modules generated by
--import-mode=importlib
would not include thechild modules as attributes of the parent modules.
#10702: Fixed error assertion handling in
pytest.approx
whenNone
is an expected or received value when comparing dictionaries.#10811: Fixed issue when using
--import-mode=importlib
together with--doctest-modules
that caused modulesto be imported more than once, causing problems with modules that have import side effects.
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.
This PR has been generated by Mend Renovate. View repository job log here.