Hi, This is my first reply in a list of replies for Grahams lengthy blog post about WSGI 3 [1]. I break it up into multiple separate threads so that this can be discussed easier.
> What should be highlighted is that for Jython, as I understand it at > least, when reading from a socket connection it returns a unicode > string. That unicode string will only have characters in the range > \u0000 through \u00FF, inclusive. Further, it is possible to transcode > that unicode string without needing to go through a separate byte > string type. On Jython 2.5 (the only one I tested) there is a 'str' and 'unicode' type and sockets return strings. I can't see much difference to cpython here. Is the Jython unicode issue really (still) relevant? I can see that IronPython has only one string type, but they are doing fine handling binary data in their unicode? ones. Regards, Armin [1]: http://blog.dscpl.com.au/2009/09/roadmap-for-python-wsgi-specification.html _______________________________________________ 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