On Mon, 03 Sep 2012 18:26:02 +0300, Serhiy Storchaka wrote: > On 03.09.12 04:42, Steven D'Aprano wrote: >> If you are *seriously* interested in debugging why string code is >> slower for you, you can start by running the full suite of Python >> string benchmarks: see the stringbench benchmark in the Tools directory >> of source installations, or see here: >> >> http://hg.python.org/cpython/file/8ff2f4634ed8/Tools/stringbench > > http://hg.python.org/cpython/file/default/Tools/stringbench > > However, stringbench is not good tool to measure the effectiveness of > new string representation, because it focuses mainly on ASCII strings > and comparing strings with bytes.
But it is a good place to start, so you can develop unicode benchmarks. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
