[Python-ideas] asyncio: factoring-out of the general mechanism

[Christoph Groth]

Hello,

I have a question/idea about the support for asynchronous programming in
Python.

With Python 3.5, support for asynchronous programming has been added to
the core Python language.  The new language features, however, are only
useful with an event loop, as provided (only?) by the asyncio stdlib
module.

I notice that already the class asyncio.AbstractEventLoop contains many
things that to me seem very specific to particular applications.  For
examples that class contains placeholders for methods that expect IP
host names and IP ports as arguments.

In a world where networking is done in other ways than through IP,
Python would be still useful.  One could keep using most of the standard
library that is not specific to IP networking.

Asynchronous programming is a concept that is way more universal than
many of the things in asyncio (IP ports, unix pipes, etc.).  Has there
been a discussion about separating the abstract bits needed for
asynchronous programming in Python from the application-specific ones?
Or would this be a bad idea for some reason?

Christoph
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 810 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20151001/2b3e1a62/attachment.sig>