[issue9282] Bug in --listfuncs option of trace.py

Alexander Belopolsky added the comment: Committed with a minor change to meet 80-character line limit. See r82997 (r82999 for 3.1). -- resolution: accepted -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker

[issue9282] Bug in --listfuncs option of trace.py

Alexander Belopolsky added the comment: This is clearly an artifact of porting to 3.x. In 2.x the code was calls = self.calledfuncs.keys() calls.sort() for filename, modulename, funcname in calls: which was translated to for filename, modulenam

[issue9282] Bug in --listfuncs option of trace.py

Eli Bendersky added the comment: I've opened issue 9315 to address the lack of unit tests for trace.py I think that this should be committed regardless, since it fixes a serious bug in the module. Adding unit tests can take time, and is less critical. -- _

[issue9282] Bug in --listfuncs option of trace.py

Terry J. Reedy added the comment: Trace.py does not appear to have a test module to add a test case to. test_trace.py currently tests the line trace facility turned on with sys.settrace. I will inquire on pydev about this. "Does trace ..." -- ___ Py

[issue9282] Bug in --listfuncs option of trace.py

Terry J. Reedy added the comment: Looking at the 2.x code, that is the obvious fix. I think this ready to commit. -- stage: -> commit review versions: -Python 3.3 ___ Python tracker __

[issue9282] Bug in --listfuncs option of trace.py

Eli Bendersky added the comment: The fix is simple one-liner, so here's a patch. -- keywords: +patch Added file: http://bugs.python.org/file18038/issue9282.1.patch ___ Python tracker ___

[issue9282] Bug in --listfuncs option of trace.py

New submission from Eli Bendersky : Running: py3d -m trace -C . --listfuncs trace_target.py Where py3d points to a freshly compiled Python 3 trunk interpreter, results in an error: functions called: Traceback (most recent call last): File "/home/eliben/python_src/eliben-py3k/Lib/runpy.py",