[Python-Dev] WSGI is now Python 3-friendly (original) (raw)
Jesse Noller jnoller at gmail.com
Sun Sep 26 03:22:53 CEST 2010
- Previous message: [Python-Dev] WSGI is now Python 3-friendly
- Next message: [Python-Dev] WSGI is now Python 3-friendly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Sep 25, 2010 at 3:56 PM, P.J. Eby <pje at telecommunity.com> wrote:
I have only done the Python 3-specific changes at this point; the diff is here if anybody wants to review, nitpick or otherwise comment:
http://svn.python.org/view/peps/trunk/pep-0333.txt?r1=85014&r2=85013&pathrev=85014 For that matter, if anybody wants to take a crack at updating Python 3's wsgiref based on the above, feel free. ;-) I'll be happy to answer any questions I can that come up in the process. (Please note: I went with Ian Bicking's "headers are strings, bodies are bytes" proposal, rather than my original "bodies and outputs are bytes" one, as there were not only some good arguments in its favor, but because it also resulted in fewer changes to the PEP, especially in the code samples.) I will continue to work on adding the other addenda/errata mentioned here: http://mail.python.org/pipermail/web-sig/2010-September/004655.html But because these are "shoulds" rather than musts, and apply to both Python 2 and 3, they are not as high priority for immediate implementation in wsgiref and do not necessarily need to hold up the 3.2 release. (Nonetheless, if anybody is willing to implement them in the Python 3 version, I will happily review the changes for backport into the Python 2 standalone version of wsgiref, and issue an updated release to include them.) Thanks!
This looks like good progress (and does not seem to block the progress of PEP 444) but would it be possible to do it as a different PEP rather then just an update; or adding an explicit "these are the differences between v1 and v2" section? It seems like it will end up different enough to be a different specification, closely related to the original, but different enough to trip up all the people maintaining current WSGI servers and apps.
jesse
- Previous message: [Python-Dev] WSGI is now Python 3-friendly
- Next message: [Python-Dev] WSGI is now Python 3-friendly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]