Martin Richard

Hm, it's more or less related to #31: currently, there is no mechanism to define how CoroutineMock should behave when it's return value is specified by a coroutine function. When...

ensure_future is a function which returns a task, you must mock it accordingly. If you want to assert that ensure_future as been called but you don't want it's behavior to...

You can make your assertions on the ensure_future_mock like you did (using assert_called_once_with). Your second approach seems the right one, but you don't need to set the return value, this...

The first solution fixes the ensure_future.assert_called_with(coroutine_mock.return_value), but I think that replacing the proxy coroutine with a new class adds one more layer of complexity (and asynctest is already very complex)....

The problem is the same with both implementations. I think ``asyncio.create_task() is a wrapper over ``asyncio.ensure_future()`` but setting the appropriate loop. Can you explain me how/why you need to check...

@argaen, I understand your point, you would like to assert that a coroutine has been scheduled asynchronously. It's seems rather complicated to do well, and that it doesn't really guarantee...

Some test files are missing in the last release (see issue #83). setup.py test has never been configured, so I'm not sure if it works, usually I run tests with...

Hi, Thanks for the report. According to the man, EPERM on epoll_ctl happens when: "The target file fd does not support epoll. This error can occur if fd refers to,...

Hi, Thanks for you suggestion. Can you give an example of API/use in code demonstrating how you would use this feature? In order to provide this feature, we need to...

Hi, This is a tricky problem because there are a lot of edge cases. CoroutineMock actually mocks a coroutine functions¹, hence if the result of a mocked function call is...