This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author scoder
Recipients brett.cannon, lemburg, python-dev, scoder
Date 2013-10-02.19:59:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
What about this: by default, we assume all runtimes to have the same major version as the Python runtime that executes the benchmark runner. If that's not the case, users must override it explicitly with a command line option, say, "--pyversions 2:3" for a reference 2.x and a comparison 3.x version of Python (i.e. in the order the programs appear on the command line).

Does that sound ok?

I'd like to avoid a trial-and-fallback approach as that would mean that any wrapper scripts would still have to support being called twice and handling the -c option in one way or another.
Date User Action Args
2013-10-02 19:59:25scodersetrecipients: + scoder, lemburg, brett.cannon, python-dev
2013-10-02 19:59:25scodersetmessageid: <>
2013-10-02 19:59:25scoderlinkissue19108 messages
2013-10-02 19:59:25scodercreate