On Fri, 2009-04-17 at 09:37 +1000, Graham Dumpleton wrote: > >> I am not sure we ended up with a final answer on all of this, but I > >> don't want to hold up mod_wsgi 3.0, which includes Python 3.0 support, > >> any longer. As such, am implementing things as per: > >> > >> http://www.wsgi.org/wsgi/Amendments_1.0 > >> > >> with exception that will not be attempting to do decoding per RFC > >> 2047. Any CGI variables not related to HTTP headers will also be > >> handled as latin-1, including SCRIPT_NAME, PATH_INFO and QUERY_STRING. > >> This should be equivalent with what wsgiref does in Python 3.X and > >> basically keeps the status quo. > >> > > That sounds fine to me, Graham, and is what I'll be implementing in my > > python3 branch for CherryPy barring any unforeseen impediments. > > Are you moving to use of empty string as end of input sentinel for > wsgi.input for case where code does actually read more than > CONTENT_LENGTH?
Sure; I think that's reasonable. It's supposed to be 'file-like'. Robert Brewer fuman...@aminus.org _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com