On Thu, Feb 2, 2012 at 04:11, Maciej Fijalkowski <fijall@gmail.com> wrote:

...

Brett Cannon wrote:

...

[snip]

...

So, to prevent this from either ending up in a dead-end because of this, we need to first decide where the canonical set of Python VM benchmarks

are

...

going to live. I say hg.python.org/benchmarks <http://hg.python.org/benchmarks> for two reasons. One is that Antoine has already done work there to port some of the benchmarks so there is at least some there that are ready to be run under Python 3 (and the tooling is in place to create separate Python 2 and Python 3 benchmark suites). Two,

On Wed, Feb 1, 2012 at 10:33 PM, Mark Shannon <mark@hotpy.org> wrote: this

...

...

can be a test of having the various VM contributors work out of hg.python.org <http://hg.python.org> if we are ever going to break the stdlib out for shared development. At worst we can simply take the changes made at pypy/benchmarks that apply to just the unladen benchmarks that exists, and at best merge the two sets (manually) into one benchmark suite so PyPy doesn't lose anything for Python 2 measurements that they have written and CPython doesn't lose any of its Python 3 benchmarks that it has created.

How does that sound?

Very sensible.

+1 from me as well. Note that "we'll have a common set of benchmarks at python.org" sounds way more pleasant than "use a subrepo from python.org".

Great! Assuming no one runs with this and starts integration, we can discuss it at PyCon and get a plan on how best to handle the merge.