On Wed, Jun 23, 2010 at 11:35:12PM +0200, Antoine Pitrou wrote: > On Wed, 23 Jun 2010 17:30:22 -0400 > Toshio Kuratomi <a.badger at gmail.com> wrote: > > Note that this assumption seems optimistic to me. I started talking to Graham > > Dumpleton, author of mod_wsgi a couple years back because mod_wsgi and paste > > do decoding of bytes to unicode at different layers which caused problems > > for application level code that should otherwise run fine when being served > > by mod_wsgi or paste httpserver. That was the beginning of Graham starting > > to talk about what the wsgi spec really should look like under python3 > > instead of the broken way that the appendix to the current wsgi spec states. > > Ok, but the reason would be that the WSGI spec is broken. Not Python 3 > itself. > Agreed. Neither python2 nor python3 is broken. It's the wsgi spec and the implementation of that spec where things fall down. From your first post, I thought you were claiming that python3 was broken since web frameworks got decoding right on python2 and I just wanted to defend python3 by showing that python2 wasn't all sunshine and roses. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20100623/413498dd/attachment.pgp>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4