> Python has been suffering through that for several years now, and has > decided to break backward compatibility and abandon the 8-bit strings -- > but using the 8-bit names for Unicode strings. I don't know what the > internal implementation is.
I found this at http://www-03.ibm.com/developerworks/blogs/page/davidmertz?entry=second_day_python_3000: All strings become Unicode (breaky), and a new bytes type lets you encode mutable arrays of 8-bit bytes. Basically, one is "text" the other is "binary data". Accompanying this will probably be a variety of mechanisms to make I/O methods inherently handle Unicode, transparently deal with decoding on open(fname) and the like (and also things like seeks). So it's a Python 3000 goal. _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
