Michael Seifert

Thanks for the reproducer! The _autouse_ fixture seems to pull in the function-scoped `event_loop` fixture as a dependency of `test_the_client` in addition to the session-scoped loop. I can verify this...

> It seems I was missing the `append=False` parameter 🤔 Strange... It partially works with that. Btw could we instead have some config parameter to not have to add this...

Thanks for the investigation. Indeed, the issue is not specifically related to autouse fixtures, but to the usage of mixed event loop scopes in general. The linked PR aims to...

> It would have been great if the huge breaking changes would have been introduced only on 1.x version. I agree that bumping to v1.0 should have been done much...

> Maybe creating v0.24 from pre v0.22 code. Also backporting any relevant bug fixes there that happened in between. It could also include all the missing unit tests that would...

@MarkusSintonen As part of the pytest-asyncio 0.24.0a0 pre-release I updated the docs with how-to guides and a section explaining the new configuration setting. Do you think this is enough to...

Thanks for sharing @gt-fm-4562 . Pytest markers are only applicable to test items, not fixture. You're saying that the configuration settings are ignored. If so, this is a separate bug....

> The following issue is still not fixed and causes a few deprecation warnings: > > * [Use of `asyncio.get_event_loop_policy` deprecated in Python 3.14-dev pytest-dev/pytest-asyncio#1025](https://github.com/pytest-dev/pytest-asyncio/issues/1025) The deprecation warnings have been...

Thanks for the example! I haven't looked at it in detail, yet, but it could be related to #868 .

Thanks for the report and the reproducer! `asyncio.run` has dedicated logic to get rid of all remaining tasks when the `asyncio.Runner` is closed (see https://github.com/python/cpython/blob/3.12/Lib/asyncio/runners.py). Although we plan to do...