Michael Seifert

I can no longer reproduce the issue using the code in the linked repository with pytest-asyncio 0.19.0. I checked CPython 3.7 up to v3.10. Please reopen if you happen to...

@crypto-only You'd only use `pytester` if you want to run pytest inside a test. This can be handy when you write a pytest plugin and want to test different configurations...

I can confirm that the provided example fails on CPython 3.7, but succeeds with CPython>=3.8 (tested on Linux x86_64). CPython 3.7 will be end of life roughly 9 months from...

As of v0.18.3 this error could be caused by an unexpected interaction with other pytest plugins that manipulate the event loop. @ReznikovRoman Can you provide a reproducible example?

Thanks for the example @suharnikov. I managed to reproduce the error. When a fixture is requested dynamically, it is looked up in pytest's fixture cache first. If it cannot be...

A fix would require that the fixture wrapper can decide dynamically whether it is run asynchronously in an event loop or synchronously. However, the fixture wrapper itself needs to be...

Your test output shows a deprecation warning about asyncio-mode. Starting with pytest-asyncio v0.19 asyncio mode defaults to strict. The error you're seeing is likely caused by wrong fixture decorators. The...

Interesting, thanks for the report. I'll look into it tomorrow.

@kiddick I cannot see anything wrong with the behaviour of pytest-asyncio in the example you provided [here](https://github.com/pytest-dev/pytest-asyncio/issues/390#issuecomment-1219288828). Your fixture returns the `_factory` async context manager. As Thomas mentioned you need...

@PeterStolz thank you for the separate issue report. Sorry to cause you extra work, but it's much easier to keep on top of existing problems and to follow discussions. >...