Le mercredi 26 septembre 2012 18:52:44 UTC+2, Paul Rubin a écrit : > Chris Angelico <ros...@gmail.com> writes: > > > 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. > > > > I like to have seen real world benchmarks against a pure UTF-8 > > implementation. That means O(n) access to the n'th character of a > > string which could theoretically slow some programs down terribly, but I > > wonder how often that actually matters in ways that can't easily be > > worked around.
The selection of a coding scheme is a problem per se. In Py33 there is a mixin of coding schemes, an artificial construction supposed to be a new coding scheme. As an exercise, pickup characters of each individual coding, toy with them and see what happen. This poor Python has not only the task to handle the bytes of a coding scheme, now it has the task to select the coding scheme it will use with probably plenty of side effects. Completely absurd. I am penalized simply because I add a French character to a French word. A character which does not belong to the same "category" of the characters composing this word. jmf -- http://mail.python.org/mailman/listinfo/python-list
