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 bobbyi
Recipients bobbyi, collinwinter, pitrou
Date 2010-11-12.19:21:49
SpamBayes Score 5.0520184e-06
Marked as misclassified No
Message-id <1289589711.2.0.279349979417.issue10397@psf.upfronthosting.co.za>
In-reply-to
Content
Steps to reproduce (requires linux because the --track-memory (-m) option to perf.py is linux-only):
hg clone http://hg.python.org/benchmarks/ py2benchmarks
mkdir py3benchmarks
cd py3benchmarks
../py2benchmarks/make_perf3.sh ../py2benchmarks
py3k perf.py -f -m -b normal_startup old_py3k new_py3k

With --track-memory, the normal_startup benchmark (which is part of the py3k benchmark group) invokes the interpreter under test as:
py3k -c 'for _ in xrange(200000): pass'

This fails on py3k due to the use of xrange, which is not caught by 2to3 since it appears inside a quoted string (the command line argument).

A patch is attached that resolves the issue by changing the for loop with xrange into a while loop.
History
Date User Action Args
2010-11-12 19:21:51bobbyisetrecipients: + bobbyi, collinwinter, pitrou
2010-11-12 19:21:51bobbyisetmessageid: <1289589711.2.0.279349979417.issue10397@psf.upfronthosting.co.za>
2010-11-12 19:21:49bobbyilinkissue10397 messages
2010-11-12 19:21:49bobbyicreate