2009/9/22 Mark Nottingham <m...@mnot.net>: > Most things is not the Web. How will you handle serving images through WSGI? > Compressed content? PDFs?
You are perhaps misunderstanding something. A WSGI application still should return bytes. The whole concept of any sort of fallback to allow unicode data to be returned for response content was purely so the canonical hello world application as per Python 2.X could still be used on Python 3.X. So, we aren't saying that the only thing WSGI applications can return is unicode strings for response content. Have you read my original blog post that triggered all this discussion this time around? Graham > On 22/09/2009, at 1:30 AM, René Dudfield wrote: > >> here is a summary: >> Apart from python3 compatibility(which should be good enough >> reason), utf-8 is what's used in http a lot these days. Most things >> layered on top of wsgi are using utf-8 (django etc), and lots of web >> clients are using utf-8 (firefox etc). >> >> Why not move to unicode? > > > -- > Mark Nottingham http://www.mnot.net/ > > _______________________________________________ > 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/graham.dumpleton%40gmail.com > _______________________________________________ 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
