[Python-ideas] Add a generic async IO poller/reactor to select module
Nick Coghlan
ncoghlan at gmail.com
Thu May 24 14:51:36 CEST 2012
On Thu, May 24, 2012 at 10:37 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Thu, May 24, 2012 at 9:50 PM, Giampaolo Rodolà <g.rodola at gmail.com> wrote:
>> poller.poll serves the same purpose of asyncore.loop, yes, but this is
>> supposed to be independent from asyncore.
>
> I'd actually like to see something like this pitched as a
> "concurrent.eventloop" PEP. PEP 3153 really wasn't what I was
> expecting after the discussions at the PyCon US 2011 language summit -
> I was expecting "here's a common event loop all the async frameworks
> can hook into", but instead we got something a *lot* more ambitious
> taht tried to merge the entire IO stack for the async frameworks,
> rather than just provide a standard way for their event loops to
> cooperate.
See the final section of my notes here:
http://www.boredomandlaziness.org/2011/03/python-language-summit-rough-notes.html
Turns out the idea of a PEP 3153 level API *was* raised at the summit,
but I'd still like to see a competing PEP that targets the reactor
level API directly.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the Python-ideas
mailing list