Message198866
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:25 | scoder | set | recipients:
+ scoder, lemburg, brett.cannon, python-dev |
2013-10-02 19:59:25 | scoder | set | messageid: <1380743965.57.0.75688163406.issue19108@psf.upfronthosting.co.za> |
2013-10-02 19:59:25 | scoder | link | issue19108 messages |
2013-10-02 19:59:25 | scoder | create | |
|