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

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

[Python-Dev] decoding errors when comparing strings

• Previous message: [Python-Dev] [patch #100912] should we keep the \xnnnn escape in unicode strings?
• Next message: [Python-Dev] decoding errors when comparing strings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

with the locale aware encoding mechanisms switched off
(sys.getdefaultencoding() =3D=3D "ascii"), I stumbled upon some
interesting behaviour:

first something that makes sense:

    >>> u"abc" =3D=3D "abc"
    1

    >>> u"=E5=E4=F6" =3D=3D "abc"
    0

but how about this one:

    >>> u"abc" =3D=3D "=E5=E4=F6"
    Traceback (most recent call last):
      File "<stdin>", line 1, in ?
    UnicodeError: ASCII decoding error: ordinal not in range(128)

or this one:

    >>> u"=E5=E4=F6" =3D=3D "=E5=E4=F6"
    Traceback (most recent call last):
      File "<stdin>", line 1, in ?
    UnicodeError: ASCII decoding error: ordinal not in range(128)

ignoring implementation details for a moment, is this really the
best we can do?

</F>

• Previous message: [Python-Dev] [patch #100912] should we keep the \xnnnn escape in unicode strings?
• Next message: [Python-Dev] decoding errors when comparing strings
• 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