[Python-Dev] [GSoC] Developing a benchmark suite (for Python 3.x) (original) (raw)
Tres Seaver tseaver at palladion.com
Fri Apr 8 14:51:04 CEST 2011
- Previous message: [Python-Dev] [GSoC] Developing a benchmark suite (for Python 3.x)
- Next message: [Python-Dev] [GSoC] Developing a benchmark suite (for Python 3.x)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/07/2011 07:52 PM, Michael Foord wrote:
Personally I think the Gsoc project should just take the pypy suite and run with that - bikeshedding about what benchmarks to include is going to make it hard to make progress. We can have fun with that discussion once we have the infrastructure and some good benchmarks in place (and the pypy ones are good ones).
So I'm still with Jesse on this one. If there is any "discussion phase" as part of the Gsoc project it should be very strictly bounded by time.
Somehow I missed seeing '[GSoC]' in the subject line (the blizzard of notification messages to the various GSoC specific lists must've snow-blinded me :). I'm fine with leaving Cython out-of-scope for the GSoC effort, just not for perf.python.org as a whole.
Tres. - --
Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2fBLgACgkQ+gerLs4ltQ67jACgozHfglhw7QQQH42hdwXy4VLX fXQAn33X/rq71BdZxmfsGn0swdeseHxJ =Ttvg -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] [GSoC] Developing a benchmark suite (for Python 3.x)
- Next message: [Python-Dev] [GSoC] Developing a benchmark suite (for Python 3.x)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]