* Jim Fulton wrote:
> On Tue, Aug 4, 2009 at 12:05 PM, P.J. Eby<p...@telecommunity.com> wrote: > > > > HTTP moves bytes, therefore WSGI should move bytes. For practical > > reasons, it would be good to *also* support strings on the application > > side, especially for application migration. However, I see no reason > > to make *servers* provide decoded strings instead of bytes. > > +1 > > I haven't had enough time to follow this and earlier encoding > discussions and so haven't commented up to now, but I've always been > uncomfortable with WSGI using anything but bytes or assuming any > encoding. I agree that application frameworks should deal with > conversion between bytes and unicode. Another +1 from the peanut gallery. nd _______________________________________________ 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
