Clarify scoped fixture rerun support - #371
Open
LouisDeconinck wants to merge 2 commits into
Open
Conversation
janmrow
reviewed
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #183.
Clarify the currently supported fixture behavior in the README: setup failures and
setup_classfailures are rerun for class-, module-, package-, and session-scoped fixtures, while successful higher-scoped fixtures remain cached across a rerun and are torn down once afterward.Add a package-scoped setup regression test and a towncrier documentation fragment.
Checks:
PYTHONPATH=src python3 -m pytest -q(227 passed, 9 skipped)uvx --from pre-commit pre-commit run --files README.rst tests/test_pytest_rerunfailures.py changes/183.doc.rstgit diff --check