Martin, > On Nov 8, 2016, at 1:39 PM, Martin Richard <mart...@martiusweb.net> wrote: > > I fully agree about coroutines, one thing though: I often see functions > returning awaitables documented as "coroutines", and I see that as a problem > since it gives the assumption that it won't be executed until processed by > the loop. > > For instance, asynctest can't identify them as coroutines, they won't get > mocked correctly: it used to be the case with aiohttp (until the wrapper > class was added to the asyncio.COROUTINE_TYPES list for python 3.5): > https://github.com/Martiusweb/asynctest/issues/23 > > In asyncio, it is still the case from some primitives of the loop > (run_in_executor(), getaddrinfo()), since they are methods of the loop > instance, I guess it's fine.
I re-read this email a few times, but I still don’t fully understand the problem you’re trying to describe. Maybe you can describe it in more detail? Yury
