Michael Seifert

The pytest-asyncio issue about `--doctest-ignore-import-errors` has been fixed as part of the pytest-asyncio v1.0.0 release.

@tony In pytest-asyncio, we have the same issue. There are [plans to remove the deprecation](https://github.com/pytest-dev/pytest-asyncio/issues/924), but until then we use pytester to [create a config that silences the warning](https://github.com/pytest-dev/pytest-asyncio/blob/5ef97bd60a3b9363c837e07cf47f19d5240cdd82/tests/markers/test_function_scope.py#L9). Does...

Thanks for the report! I can reproduce the issue with pytest-asyncio v0.23.2. I can also reproduce it with pytest-asyncio v0.21.1, though: ```python $ python -X dev -m pytest --setup-show =====...

The issue is reproducible in v1.0.0a1.

Both stack traces complain about queues or tasks being attached to different event loops. Two things come to my mind: 1. The event_loop fixture closes any existing loop and returns...

@M1ha-Shvn Any updates on your issue?

Maybe there's a smarter way for pytest-asyncio to detect loop changes. I'll leave the issue open for the time being.

Thanks for the issue report! I fully agree that pytest-asyncio should add a test environment that uses pre-release versions of its dependencies. A first step towards this might be adding...

I'm not sure how we can make use of eager tasks, since I haven't used them, yet. My current understanding is that it is intended as a performance improvement. Other...

The use of _event_loop_ is deprecated. We should adjust the docs to reflect that. The rationale is summarized here: https://github.com/pytest-dev/pytest-asyncio/issues/706#issuecomment-2282780197