<br><br><div class="gmail_quote">On Mon, Mar 18, 2013 at 11:00 PM, Tim Allen <span dir="ltr"><<a href="mailto:screwtape@froup.com" target="_blank">screwtape@froup.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In Guido's keynote at PyCon 2013, apparently he talked about adding an<br>
async I/O module to Python 3.4. It looks like his slides can be viewed<br>
here:<br>
<br>
<a href="https://www.dropbox.com/s/xknbe58zcvjhzhv/PyCon2013.pptx" target="_blank">https://www.dropbox.com/s/xknbe58zcvjhzhv/PyCon2013.pptx</a><br>
<br>
...while this is the PEP he's talking about:<br>
<br>
<a href="http://www.python.org/dev/peps/pep-3156/" target="_blank">http://www.python.org/dev/peps/pep-3156/</a><br>
<br>
At first glance, the proposed reactor API looks very much like Twisted's<br>
(or, to be fair, GTK's, or possibly any number of other async event loop<br>
I'm less familiar with) but rather than Deferreds and callbacks, the API<br>
will be based around Futures (similar, but not identical, to Python<br>
3.2's concurrent.futures.Future class), and an inlineCallbacks-style<br>
decorator for generators.<br></blockquote><div><br></div><div>There's two parts: one is a standardized, pluggable API for event loops. It's explicitly based on Twisted's, and will be easy to add a Twisted implementation. The generator thing is layered on top, and somewhat optional, in theory.</div>
<div><br></div><div>-Itamar</div></div>