It seems most pypy benchmarks are moved from cpython and as a result they fail because a particular module is unavalable.
A more pragmatic approach is to go through the list of benchmarks and either accept current python code for pypy or fail on purpose if python code is too un-pypy-like. Later on, hopefully, someone volunteers to rewrite problem benchmarks. This, btw, is almost status quo. how about that? both visibility for pypy and avoidance of worst problems... d. On 5 April 2011 08:14, Armin Rigo <ar...@tunes.org> wrote: > Hi Isaac, > > If you're not interested in this discussion and just want a Yes or No > answer to precisely the following question: > > "should PyPy be added to the benchmarks game's site, with no changes > whatsoever to any of the Python benchmarks that are there so far?" > > then the answer is No. We are not interested in the results of PyPy > on such skewed benchmarks, and publishing them would only add to the > general confusion. > > > Armin > _______________________________________________ > pypy-dev@codespeak.net > http://codespeak.net/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev