Antoine Pitrou added the comment: > The overhead of 2to3 isn't too bad, especially because only a subset > of the benchmarks is translated in the first place.
Well, the biggest time is spent translating the third-party libraries, not benchmark files. Also, it's simply tedious manual work (you have to create a separate directory etc.). > It is more important that there is better documentation than there is > now, it seems that you're supposed to use either '-b 2n3' or > make_perf3.sh with '-b py3k'. Neither of which are mentioned in > README.txt. That's because the benchmark suite was initially 2.x-only, and the "make_perf3.sh" was a quick hack to make some of the benchmarks work on 3.x. Nowadays the goal is for benchmark files to be 2.x and 3.x compatible in the same codebase, so that only third-party libs remain to translate. Adding 3.x-compatible versions of the third-party libs would eliminate that last step. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17449> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
