Using asyncio workers in a `concurrent.futures` interface

[Marko Rauhamaa]

Ian Kelly <ian.g.kelly at gmail.com>:

> On Tue, Aug 12, 2014 at 11:02 AM, cool-RR <ram.rachum at gmail.com> wrote:
>> And that's it, no coroutines, no `yield from`. Since, if I understand
>> correctly, asyncio requires a mainloop, it would make sense for the
>> AsyncIOExecutor to have a thread of its own in which it could run its
>> mainloop.
>
> I think that putting the event loop in a separate thread would be
> necessary if the intention is that the executor be invoked from
> outside. I'm not aware of this work having been done, but it sounds
> perfectly feasible.

Multithreading will require normal locking to protect critical sections.
Care must be taken to never yield while holding a threading lock.


Marko