[Async-sig] A possible tiny step towards event loop interoperability

[Guido van Rossum]

OK, that helps. Could you talk me through the crucial
incompatibilities here? (If that's too  much to ask I'm also happy to
leave this up to the experts -- I trust that there's more than enough
brainpower here to come up with a solution that works for all
concerned.)

On Fri, Jun 3, 2016 at 5:45 PM, Ben Darnell <ben at bendarnell.com> wrote:
> On Fri, Jun 3, 2016 at 8:43 PM, Guido van Rossum <guido at python.org> wrote:
>>
>> Could someone point me to the specific code that's considered the
>> coroutine runner in asyncio and Tornado? I've been immersed in asyncio
>> for so long that I don't know which part you're talking about. :-(
>
>
> asyncio.Task and tornado.gen.Runner. Basically the thing that calls next()
> and send() on generator objects.
>
>>
>>
>> On Fri, Jun 3, 2016 at 5:26 PM, Nathaniel Smith <njs at pobox.com> wrote:
>> > On Fri, Jun 3, 2016 at 5:14 PM, Ben Darnell <ben at bendarnell.com> wrote:
>> >> I think this could be useful, but's answering the question of "what
>> >> coroutine runner is this", not "what event loop is this".
>> >
>> > Thanks, that's definitely a better way to put it.
>> >
>> > -n
>> >
>> > --
>> > Nathaniel J. Smith -- https://vorpus.org
>> > _______________________________________________
>> > Async-sig mailing list
>> > Async-sig at python.org
>> > https://mail.python.org/mailman/listinfo/async-sig
>> > Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>>
>>
>> --
>> --Guido van Rossum (python.org/~guido)
>
>



-- 
--Guido van Rossum (python.org/~guido)