-
- Notifications
You must be signed in to change notification settings - Fork 2.9k
move fixture finalizing to pytest_fixture_teardown hook #12164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| I was just about to submit a PR with almost identical code changes when I discovered yours :) |
90172a2 to 28169e9 Compare | that failing test does not seem to be related to the contributed code |
RonnyPfannschmidt left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks good to me, how does this interact with pytest-asyncio?
For pytest-asyncio, everything should work without additional improvements |
bluetech left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking "Request changes" as per my comment on the issue: #12163 (comment)
@ShurikMen @rplevka please let me know in the issue if you have any specific use case for pytest_fixture_teardown instead of extending pytest_fixture_post_finalizer
I use it like this #12163 (comment) |
| @RonnyPfannschmidt help, please? I think this has been stale for some time. We think the change makes perfect sense and we would really find it useful in our project. |
a76d95a to a99ddff Compare for more information, see https://pre-commit.ci
| im also waiting for a reply from @bluetech - i think the concerns mentioned need to be addressed |
| @RonnyPfannschmidt Are there any concerns that should be addressed by the community? If so, could you please let us know what are these? I believe that concerns @bluetech had were answered in #12163. |
for more information, see https://pre-commit.ci
| @bluetech ping - can we add a fresh comment here whats still missing to progress this - its unclear to me if the reply in the issue addressed your concern sufficiently or not |
| i did some re-reading - and the concerns haven't been resolved - i need a better understanding of the use-case and actual exampel of the use-ases involved as im getting a X-Y problem gut feeling |
solution #12163