Article on the future of Python

Chris Angelico rosuav at gmail.com
Wed Sep 26 05:55:12 EDT 2012


On Wed, Sep 26, 2012 at 7:31 PM,  <wxjmfauth at gmail.com> wrote:
> you are correct. But the price you pay for this is extremely
> high. Now, practically all characters are affected, espacially
> those *in* the Basic *** Multilingual*** Plane, these characters
> used by non "American" user (No offense here, I just use this
> word for ascii/latin-1).
>
> I'm ready to be considered as an idiot, but I'm not blind.
> As soon as I tested these characters, Py3.3 performs really
> badly. It seems to me it is legitimate to consider, there
> is a serious problem here.

We've been over this thread. The only reason you're counting 3.3 as
worse is because you're comparing against a narrow build of Python
3.2. Narrow builds are **BUGGY** and this needed to be resolved.

When you compare against a wide build, semantics of 3.2 and 3.3 are
identical, and then - and ONLY then - can you sanely compare
performance. And 3.3 stacks up much better.

ChrisA



More information about the Python-list mailing list