Martin Richard

Hi, Did you find a way to solve or work around this issue ?

Yes, I believe that users who need old style coroutines can use an older version of asynctest. On Wed, Jan 29, 2020, 03:53 Cooper Lees wrote: > Since 3.4 is...

Hi, First of all, sorry for the very late reply. To keep things short: I'll not work on asynctest anymore, and I believe unittest.mock.AsyncMock in combination with pytest is probably...

Hi, Thank you for the PR. The first error est related to the way tests must be called: python -m unittest test/ The ``test/`` is required, and in fact I...

As I just commented in the other bug, maybe this will solve most of the problems people have with Python 3.8, but people should migrate to AsyncMock. I will try...

Can you provide a stack trace?

Since AsyncMock landed in Python 3.8, people should use AsyncMock and . AsyncMock breaks asynctest in ways that make it hard to fix correctly, and I have time/resources to spend...

Hi, `unittest.mock.AsyncMock` borrows most of the concepts and API from `asynctest.CoroutineMock`. Enventually (for projects which only support 3.8+), I believe that AsyncMock should become the class to use. For asynctest,...

Hi, I discussed with Lisa Roach who contributed this to cPython. AsyncMock is actually borrowing code from CoroutineMock, which is great but makes it hard to make asynctest compatible with...

Hello, `self.assertAsyncRaises` accepts an awaitable as argument so you should write: await self.assertAsyncRaises(ValueError, x(1, 2)) It's actually a very simple shorthand: https://asynctest.readthedocs.io/en/latest/_modules/asynctest/case.html#TestCase.assertAsyncRaises assertAsyncRaises don't accept the coroutine function + args...