Yes. This difficulty is exactly why fixing this had to be rolled into the major incompatibilities introduced by 3.0.
http://docs.python.org/dev/3.0/whatsnew/3.0.html#text-vs-data-instead-of-unicode-vs-8-bit On Wed, Jan 21, 2009 at 12:11 PM, Mark Slee <[email protected]> wrote: > My personal experience dealing with Python string-handling has created a > lot of headaches. The distinction between the primitive unicode vs. string > types is subtle but can cause a lot of weird foibles like this. > -- Ted Dunning, CTO DeepDyve 4600 Bohannon Drive, Suite 220 Menlo Park, CA 94025 www.deepdyve.com 650-324-0110, ext. 738 858-414-0013 (m)
