Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Graham Dumpleton
Okay, thanks for all that. Now for next question. So far we haven't addressed how wsgi.file_wrapper should work for Python 3.0. Already in existing versions of Python usage of wsgi.file_wrapper may be unclear in that there are portability concerns between UNIX and Windows over fact that FILE objec

Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Phillip J. Eby
At 11:41 AM 3/25/2008 -0500, Ian Bicking wrote: >Phillip J. Eby wrote: >>At 11:04 AM 3/25/2008 -0500, Ian Bicking wrote: >>>Phillip J. Eby wrote: It says that in versions of Python where 'str is unicode' (i.e. Jython, IronPython, and Python 3000), then the specification should be read

Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Robert Brewer
Graham Dumpleton wrote: > 3. When running under Python 3, servers MUST provide CGI HTTP > variables as strings, decoded from the headers using HTTP standard > encodings (i.e. latin-1 + RFC 2047) > > Can someone give a practical example of where RFC 2047 fits into this > and how one is meant to han

Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Ian Bicking
Phillip J. Eby wrote: > At 11:04 AM 3/25/2008 -0500, Ian Bicking wrote: >> Phillip J. Eby wrote: >>> It says that in versions of Python where 'str is unicode' (i.e. >>> Jython, IronPython, and Python 3000), then the specification should >>> be read to define "string" as a unicode string whose cha

Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Phillip J. Eby
At 11:04 AM 3/25/2008 -0500, Ian Bicking wrote: >Phillip J. Eby wrote: >>It says that in versions of Python where 'str is unicode' (i.e. >>Jython, IronPython, and Python 3000), then the specification should >>be read to define "string" as a unicode string whose characters can >>be expressed in l

Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Ian Bicking
Phillip J. Eby wrote: > At 04:54 PM 3/25/2008 +1100, Graham Dumpleton wrote: >> Why are servers and gateways being made to accept strings when the >> preference is for applications to produce bytes for both? Is this >> acknowledgment that getting people to convert WSGI applications to >> produce by

Re: [Web-SIG] Clarifications on Python 3.0 and WSGI.

2008-03-25 Thread Phillip J. Eby
At 04:54 PM 3/25/2008 +1100, Graham Dumpleton wrote: >Why are servers and gateways being made to accept strings when the >preference is for applications to produce bytes for both? Is this >acknowledgment that getting people to convert WSGI applications to >produce bytes may be a problem? Yep. >Th