On Thu, Sep 16, 2010 at 1:04 PM, P.J. Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
* Clarifying the encoding of environ values (locale+surrogateescape vs. latin1, TBD)<br></blockquote><div><br>locale+surrageescape would be insanity! CGI will just require some configuration with respect to the environment. Anyway, I suspect CGI only really works because: (a) people using CGI are sticking to ASCII, (b) they've fixed stuff up in their apps, (c) they just produce garbage and no one cares.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
* Making the streams and all output values byte strings ('str' on 2.x, 'bytes' on 3.x), leaving everything else "native" strings ('str' on both 2.x and 3.x)<br>
<br>
* Any other minor errata/clarifications that the folks with the requisite experience (e.g. Robert, Ian, Graham -- not an exclusive list, but at least they all have both heavy WSGI implementations under their belts and 3.x experience) think are absolutely necessary to resolve open questions for Python 3.2 WSGI implementations.<br>
</blockquote></div><br>There are some simple errata, most of which I believe web3 covers (in addition to other things it covers).<br><br>I think everyone is on board with:<br><br> status, headers, app_iter = app(environ)<br>
<br>Web3 proposed a different order, but it seems clear from the thread that people prefer the more natural order, and web3 authors don't particularly object.<br clear="all"><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>