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

2009-05-05 Thread Ian Bicking
On Tue, May 5, 2009 at 10:14 PM, Graham Dumpleton < graham.dumple...@gmail.com> wrote: > 2009/5/6 Ian Bicking : > > Philip Jenvey brought this to my attention: > > > > http://www.python.org/dev/peps/pep-0383/ > > > > It's a UTF8 encoding and decoding scheme that encodes illegal bytes in > such >

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

2009-05-05 Thread Graham Dumpleton
2009/5/6 Ian Bicking : > Philip Jenvey brought this to my attention: > >   http://www.python.org/dev/peps/pep-0383/ > > It's a UTF8 encoding and decoding scheme that encodes illegal bytes in such > a way that you can decode to get the original bytes object, and thus > transcode to another encoding.

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

2009-05-05 Thread Ian Bicking
Philip Jenvey brought this to my attention: http://www.python.org/dev/peps/pep-0383/ It's a UTF8 encoding and decoding scheme that encodes illegal bytes in such a way that you can decode to get the original bytes object, and thus transcode to another encoding. It's intended for cases exactly l

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

2009-05-05 Thread Robert Brewer
Graham Dumpleton wrote: > 2009/5/5 Armin Ronacher : >> Graham Dumpleton wrote: >>> I can't see but have choice but to pass such settings through as >>> strings, else more than likely would cause problems for applications. >>> Problem is it isn't clear what encoding stuff can be in Apache >>> config

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

2009-05-05 Thread Graham Dumpleton
2009/5/5 Armin Ronacher : > Hi, > > Graham Dumpleton wrote: >> I can't see but have choice but to pass such settings through as >> strings, else more than likely would cause problems for applications. >> Problem is it isn't clear what encoding stuff can be in Apache >> configuration. At the moment