I just pushed the changes.<br><br><div class="gmail_quote">On Fri, Sep 14, 2012 at 4:19 PM, Brett Cannon <span dir="ltr">&lt;<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

So I managed to get the following benchmarks moved into the unladen repo (not pushed yet until I figure out some reasonable scaling values as some finish probably too fast and others go for a while):<div><br></div><div>chaos</div>


<div>fannkuch</div><div>meteor-contest (renamed meteor_contest)</div><div>spectral-norm (renamed spectral_norm)</div><div>telco</div><div>bm_mako (renamed bm_mako_v2; also pulled in mako 0.9.7 for this benchmark)</div><div>


go</div><div>hexiom2</div><div>json_bench (renamed json_dump_v2)</div><div>raytrace_simple (renamed raytrace)</div><div><br></div><div>Most of the porting was range/xrange related. After that is was str/unicode. I also stopped having the benchmarks write out files as it was always to verify results and not a core part of the benchmark.</div>


<div><br></div><div>That leaves us with the benchmarks that rely on third-party projects. The chameleon benchmark can probably be ported as chameleon has a version released running on Python 3. But django and html5lib have only in-development versions that support Python 3. If we want to pull in the tip of their repos then those benchmarks can also be ported now rather than later. People have opinions on in-dev code vs. released for benchmarking?</div>


<div><br></div><div>There is also the sphinx benchmark, but that requires getting CPython&#39;s docs building under Python 3 (see <a href="http://bugs.python.org/issue10224" target="_blank">http://bugs.python.org/issue10224</a>).</div>


</blockquote></div><br>