This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author effbot
Recipients
Date 2007-08-21.08:48:42
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
"Most other string operations work nicely between normal and unicode strings"

Nope.  You *always* get errors if you mix Unicode with NON-ASCII data (unless you've messed up the system's default encoding, which is a bad thing to do if you care about portability).  Some examples:

>>> chr(128) + u"foo"
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in range(128)
>>> u"foo".find(chr(128))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in range(128)

etc.  If there's a bug here, it's that you get a TypeError instead of a ValueError subclass.
History
Date User Action Args
2007-08-23 14:59:11adminlinkissue1772788 messages
2007-08-23 14:59:11admincreate