Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-April/003750.html below:

[Python-Dev] Re: Python 1.6a2 Unicode bug (was Re: comparing strings and ints)

• Previous message: [Python-Dev] Re: Python 1.6a2 Unicode bug (was Re: comparing strings and ints)
• Next message: [Python-Dev] Re: Python 1.6a2 Unicode bug (was Re: comparing strings and ints)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I wrote:
>A utf-8-encoded 8-bit string in Python is *not* a string, but a "ByteArray".

Another way of putting this is:
- utf-8 in an 8-bit string is to a unicode string what a pickle is to an
object.
- defaulting to utf-8 upon coercing is like implicitly trying to unpickle
an 8-bit string when comparing it to an instance. Bad idea.

Defaulting to Latin-1 is the only logical choice, no matter how
western-culture-centric this may seem.

Just

• Previous message: [Python-Dev] Re: Python 1.6a2 Unicode bug (was Re: comparing strings and ints)
• Next message: [Python-Dev] Re: Python 1.6a2 Unicode bug (was Re: comparing strings and ints)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4