Michael Seifert

> I was using pytest-asyncio master to verify that the Issue still exists. I ran it again on the latest pypi version (asyncio-0.18.3 and python 3.10.4) and it still crashes....

Thanks for the contribution! The linked issue is not the only request of that feature. There is also #222. We closed #222 in favour of #235, which intends to used...

Thanks for uploading the latest version. I had some time to look into the issue that causes `ResourceWarning`s in the tests. The culprit seems to be `test_event_loop_scope.py::test_4`. The test case...

I modified `test_event_loop_scope.py::test_4` accordingly to avoid side-effects in other tests. The PR has been rebased and two typing issues have been addressed.

There are very few things that need to be solved for the corresponding PR to get merged. Hence I'm marking this as good first issue.

> Is there any better way right now? Unfortunately, there is currently no publicly supported way to inspect tests in the way you want. > I would have expected this...

Thanks for the bug report and for narrowing down the issue to different `pytest-asyncio` versions! We're currently trying to get an understand what issues are still relevant and which of...

The issue is reproducible in v0.19.0.

The culprit seems to be the implementation of `pytest_pycollect_makeitem`. The function injects the `event_loop` and `request` dependencies into async fixture definitions. The `pytest_pycollect_makeitem` hook calls `_preprocess_async_fixtures` which essentially reimplements part...

My understanding is that there are two questions in the room: 1. Does `pytest-asyncio` work with `pytest-bdd` when using async test steps? 2. Can `pytest-asyncio` be used to provide support...