[New-bugs-announce] [issue10397] Unified Benchmark Suite fails on py3k with --track-memory

Bobby Impollonia report at bugs.python.org
Fri Nov 12 20:21:51 CET 2010

New submission from Bobby Impollonia <bobbyi at gmail.com>:

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.

assignee: collinwinter
components: Benchmarks
files: perf.patch
keywords: patch
messages: 121060
nosy: bobbyi, collinwinter, pitrou
priority: normal
severity: normal
status: open
title: Unified Benchmark Suite fails on py3k with --track-memory
type: behavior
versions: Python 3.2
Added file: http://bugs.python.org/file19582/perf.patch

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list