It sounds like async could be a separate PEP, if that will make acceptance of PEP 444 easier.<br><br><div class="gmail_quote">On Sun, Jan 2, 2011 at 12:38 PM, Alice Bevan–McGregor <span dir="ltr"><<a href="mailto:alice@gothcandy.com">alice@gothcandy.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 2011-01-02 11:14:00 -0800, Chris McDonough said:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I'd suggest we just embrace it, adding minor tweaks as necessary, until we reach some sort of technical impasse it doesn't address.<br>
</blockquote></blockquote>
<br></div>
Async is one area that 3333 does not cover, and that by not having a standard which incorporates async means competing, incompatible solutions have been created.<div class="im"><br>
<br>
On 2011-01-02 12:00:39 -0800, Guido van Rossum said:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Actually that does sound like an opinion on the technical merits. I can't tell though, because I'm not familiar enough with PEP 444 to know what the critical differences are compared to PEP 3333. Could someone summarize?<br>
</blockquote>
<br></div>
Async, distinction between byte strings (type returned by socket.read), native strings, and unicode strings, thorough unicode decoding (moving some of the work from middleware to the server), simplified call syntax (no more start_response), and clear, consice language with easy references via numbered lists.<br>
<br>
The async part is an idea in my head that I really do need to write down, clarified with help from agronholm on IRC. The futures PEP is available as a pypi installable module, is core in 3.2, and seems to provide a simple enough abstract (duck-typed) interface that it should be usable as a basis for async in PEP 444.<br>
<br>
There are parts I need to add back, of course. file_wrapper, examples, rationale, and references being a few of the items not yet rewritten.<div><div></div><div class="h5"><br>
<br>
- Alice.<br>
<br>
<br>
_______________________________________________<br>
Web-SIG mailing list<br>
<a href="mailto:Web-SIG@python.org" target="_blank">Web-SIG@python.org</a><br>
Web SIG: <a href="http://www.python.org/sigs/web-sig" target="_blank">http://www.python.org/sigs/web-sig</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/web-sig/guido%40python.org" target="_blank">http://mail.python.org/mailman/options/web-sig/guido%40python.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>--Guido van Rossum (<a href="http://python.org/~guido">python.org/~guido</a>)<br>