[Async-sig] A possible tiny step towards event loop interoperability
Cory Benfield
cory at lukasa.co.uk
Fri Jun 3 18:54:13 EDT 2016
> On 3 Jun 2016, at 15:26, Nathaniel Smith <njs at pobox.com> wrote:
>
> Convincing everyone to agree on a single event loop API sounds hard.
>
> But maybe it would be useful to start with a baby step of defining a
> standard way for a coroutine to ask the event loop who it is, e.g.
>
> await what_event_loop_is_this()
> -> "asyncio"
> -> "curio"
> -> ...
How do we ensure that this function is always available in the global namespace, or alternatively that it’s always available in a *consistent* namespace?
Cory
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/async-sig/attachments/20160603/766b9952/attachment.sig>
More information about the Async-sig
mailing list