[Web-SIG] Request for Comments on upcoming WSGI Changes
graham.dumpleton at gmail.com
Sun Sep 20 22:52:16 CEST 2009
2009/9/21 Armin Ronacher <armin.ronacher at active-4.com>:
>> IMO, this strongly suggests that it's the stdlib or Python 3 that's
>> broken here. How much of the stdlib are we talking about needing to
>> reimplement, aside from cgi.FieldStorage?
> I'm already creating a patch for urllib which currently requires
> unicode. I'm not sure about what to do with cgi.FieldStorage, in
> general I would not recommend using the cgi module for WSGI applications
> at all! If we would go with bytes for the WSGI 1.0 spec on Python 3 a
> WSGI server also has to decode that data from the Server again.
> Also (something I haven't yet filed as a bug because I guess there will
> be more changes involved) the HTTP server in Python 3.1 does not support
> non-ASCII headers.
Read the following first:
There the ones I know about that affect cgi.FieldStorage.
More information about the Web-SIG