Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Terry Reedy <tjreedy@udel.edu>
Subject: Mistake or Troll (was Re: =?UTF-8?B?J1N0cmHDn2UnICgnU3RyYXNzZScp?= =?UTF-8?B?IGFuZCBQeXRob24gMik=?=
Date: Mon, 13 Jan 2014 18:05:04 -0500
References: <30dfa6f1-61b2-49b8-bc65-5fd18d498c38@googlegroups.com> <lb0826$k8h$1@r01.glglgl.de> <d9170600-01e2-4417-af93-87120bffa940@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
In-Reply-To: <d9170600-01e2-4417-af93-87120bffa940@googlegroups.com>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.5432.1389654325.18130.python-list@python.org>
Lines: 62
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:63866

On 1/13/2014 4:54 AM, wxjmfauth@gmail.com wrote:

> I'm afraid I'm understanding Python (on this
> aspect very well).

Really?

> Do you belong to this group of people who are naively
> writing wrong Python code (usually not properly working)
> during more than a decade?

To me, the important question is whether this and previous similar posts =

are intentional trolls designed to stir up the flurry of responses they=20
get or 'innocently' misleading or even erroneous. If your claim of=20
understanding Python and Unicode is true, then this must be a troll=20
post. Either way, please desist, or your access to python-list from=20
google-groups may be removed.

> '=C3=9F' is the the fourth character in that text "Stra=C3=9Fe"
> (base index 0).

As others have said, in the *unicode text "Stra=C3=9Fe", '=C3=9F' is the =
fifth=20
character, at character index 4, ...

> This assertions are correct (byte string and unicode).

whereas, when the text is encoded into bytes, the byte index depends on=20
the encoding and the assertion that it is always 4 is incorrect. Did you =

know this or were you truly ignorant?

>>>> sys.version
> '2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)]'
>>>> assert 'Stra=C3=9Fe'[4] =3D=3D '=C3=9F'

Sometimes true, sometimes not.

>>>> assert u'Stra=C3=9Fe'[4] =3D=3D u'=C3=9F'

> PS Nothing to do with Py2/Py3.

This issue has everything to do with Py2, where 'Stra=C3=9Fe' is encoded =

bytes, versus Py3, where 'Stra=C3=9Fe' is unicode text where each charact=
er=20
of that word takes one code unit, whether each is 2 bytes or 4 bytes.

If you replace '=C3=9F' with any astral (non-BMP) character, this issue=20
appears even for unicode text in 3.2-, where an astral character=20
requires 2, not 1, code units on narrow builds, thereby screwing up=20
indexing, just as can happen for encoded bytes. In 3.3+, all characters=20
use 1 code unit and indexing (and slicing) always works properly. This=20
is another unicode issue where you appear not to understand, but might=20
just be trolling.

--=20
Terry Jan Reedy