Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!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: Re: How do I display unicode value stored in a string variable using ord()
Date: Sat, 18 Aug 2012 16:09:14 -0400
References: <f801e06f-f7b2-4aca-b352-66856a939746@googlegroups.com> <308df2af-abe7-4043-b199-0a39f440e0ab@googlegroups.com> <502f8a2a$0$29978$c3e8da3$5496439d@news.astraweb.com> <d575737d-c1e3-47db-9c7b-10fe0300cba7@googlegroups.com> <mailman.3457.1345305136.4697.python-list@python.org> <4c62a649-bc21-4e47-9c0f-acb1b1e70e36@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:14.0) Gecko/20120713 Thunderbird/14.0
In-Reply-To: <4c62a649-bc21-4e47-9c0f-acb1b1e70e36@googlegroups.com>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3472.1345320581.4697.python-list@python.org>
Lines: 55
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:27329

On 8/18/2012 12:38 PM, wxjmfauth@gmail.com wrote:
> Sorry guys, I'm not stupid (I think). I can open IDLE with
> Py 3.2 ou Py 3.3 and compare strings manipulations. Py 3.3 is
> always slower. Period.

You have not tried enough tests ;-).

On my Win7-64 system:
from timeit import timeit

print(timeit(" 'a'*10000 "))
3.3.0b2: .5
3.2.3: .8

print(timeit("c in a", "c  =3D '=E2=80=A6'; a =3D 'a'*10000"))
3.3: .05 (independent of len(a)!)
3.2: 5.8  100 times slower! Increase len(a) and the ratio can be made as =

high as one wants!

print(timeit("a.encode()", "a =3D 'a'*1000"))
3.2: 1.5
3.3:  .26

Similar with encoding=3D'utf-8' added to call.

Jim, please stop the ranting. It does not help improve Python. utf-32 is =

not a panacea; it has problems of time, space, and system compatibility=20
(Windows and others). Victor Stinner, whatever he may have once thought=20
and said, put a *lot* of effort into making the new implementation both=20
correct and fast.

On your replace example
 >>> imeit.timeit("('ab=E2=80=A6' * 1000).replace('=E2=80=A6', '=E2=80=A6=
=E2=80=A6')")
 > 61.919225272152346
 >>> timeit.timeit("('ab=E2=80=A6' * 10).replace('=E2=80=A6', '=C5=93=E2=80=
=A6')")
 > 1.2918679017971044

I do not see the point of changing both length and replacement. For me,=20
the time is about the same for either replacement. I do see about the=20
same slowdown ratio for 3.3 versus 3.2 I also see it for pure search=20
without replacement.

print(timeit("c in a", "c  =3D '=E2=80=A6'; a =3D 'a'*1000+c"))
# .6 in 3.2.3, 1.2 in 3.3.0

This does not make sense to me and I will ask about it.

--=20
Terry Jan Reedy