Ian Bicking wrote:
The proposal that seemed to work best was to keep the environ as str (i.e.,
unicode in Python 3), and eliminate the problematic SCRIPT_NAME and
PATH_INFO, replacing them with url-encoded values.
Ah, OK, if that's where we got to I'm happy with that - as long as the
2009/11/26 And Clover and...@doxdesk.com:
Whilst in principle I kind of agree with Malthe that keeping the CGI-derived
environ separate from items like wsgi.input would be appropriate, in
practice I don't give a stuff about it: the merged dictionary causes no
practical problems, and changing
http://wiki.python.org/moin/WebFrameworks seems to be the place where folks are
registering their respective web frameworks.
I'd like to move some of the frameworks which are currently in the various
categories which haven't been active in a few years. In particular, I'd like
to move any
I move to bless mod_wsgi's definition of WSGI 1.1 [1] as the official
definition of WSGI 1.1, which describes how to implement WSGI adapters for both
Python 2.x and 3.x. It may not be perfect, but, it's been implemented twice,
and seems ot have no fatal flaws (it doesn't do any lossy
