Skip to content
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

hook/mechanism to await awaitable results of fixtures/test results (asyncio/anyio/trio) #9962

Open
RonnyPfannschmidt opened this issue May 15, 2022 · 2 comments
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@RonnyPfannschmidt
Copy link
Member

currently pytest plugins have to replicate a number of mechanisms to handle async fixtures

#207 was originally intended to help with that, but was more broad than necessary

with #7337 being soon integrated,
the interface should be narrowed and coordinated with the asyncio/trio/curio plugins

@Zac-HD Zac-HD added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label May 16, 2022
@Zac-HD
Copy link
Member

Zac-HD commented Jul 6, 2024

As a maintainer of pytest, trio, anyio, and pytest-trio (anyio has the pytest plugin built-in), I think the status quo is working pretty well. Anything else we need to do before closing this?

@RonnyPfannschmidt
Copy link
Member Author

We absolutely should upstream a part of it

I want to be in a position where nextitemcan be removed from the runtest protocol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Development

No branches or pull requests

2 participants