Michael Seifert

Results 244 comments of Michael Seifert

See https://github.com/pytest-dev/pytest-asyncio/issues/248

This issue seems to have been fixed. A user reported a working integration between flaky and pytest-asyncio for v0.18. I suppose it would be reasonable to close this issue.

The issue has been resolved for CPython 3.12 and the patch was backported to CPython 3.10 and CPython 3.11. 3.10.9 is scheduled for 2022-12-05 and 3.11.1 should be released in...

The issue continues to be valid. If anyone wants to resolve it for Python 3.8 or 3.9, they're welcome to provide a backport that can be included in pytest-asyncio.

I can no longer reproduce the error of the OP as of pytest-asyncio 0.21.1. Hence, I'll mark this issue as resolved.

@poppyi-domain Pytest-asyncio v0.23 supports running tests in different event loops. There's a loop for each level of the test suite (session, package, module, class, function). However, pytest-asyncio wrongly assumes that...

This PR introduces a "runner" abstraction and adds the timeout functionality. This is also the general way forward for pytest-asyncio. Preferably, these two things should happen in separate PRs, one...

@priyanshu-panwar Of course, give it a try. The existing PR is generally good. My main concerns are the use of non-public CPython APIs (i.e. the use of `asyncio.runners._cancel_all_tasks`) and the...

@samypr100 I fully agree that using asyncio.Runner is the way to go for pytest-asyncio in the future. This is tightly connected to #127. As we speak, pytest-asyncio v0.23 is in...

@KelvinSan There has been no progress on this from the pytest-asyncio side. In the meantime, the pytest-bdd issue linked by the OP received some attention. One comment presents a "comaptibility...