[pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks

Brian Kearns tracker at bugs.pypy.org
Sun Mar 17 21:28:28 CET 2013


New submission from Brian Kearns <bdkearns at gmail.com>:

$ ./pypy/bin/pyinteractive.py -v
PyPy 2.0.0-beta1 in StdObjSpace on top of Python 2.7.3 (startuptime: 10.27 secs)
>>>> raise ValueError
|| Traceback (interpreter-level):
||   File "./pypy/bin/../../pypy/interpreter/main.py", line 103, in run_toplevel
||     f()
||   File "./pypy/bin/../../pypy/interpreter/interactive.py", line 192, in doit
||     code.exec_code(self.space, self.w_globals, self.w_globals)
||   File "./pypy/bin/../../pypy/interpreter/eval.py", line 33, in exec_code
||     return frame.run()
||   File "./pypy/bin/../../pypy/interpreter/pyframe.py", line 141, in run
||     return self.execute_frame()
||   File "./pypy/bin/../../pypy/interpreter/pyframe.py", line 175, in 
execute_frame
||     executioncontext)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 81, in dispatch
||     next_instr = self.handle_bytecode(co_code, next_instr, ec)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 89, in 
handle_bytecode
||     next_instr = self.handle_operation_error(ec, operr)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 87, in 
handle_bytecode
||     next_instr = self.dispatch_bytecode(co_code, next_instr, ec)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 259, in 
dispatch_bytecode
||     res = meth(oparg, next_instr)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 558, in 
RAISE_VARARGS
||     raise operror
|| Traceback (interpreter-level):
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 87, in 
handle_bytecode
||     next_instr = self.dispatch_bytecode(co_code, next_instr, ec)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 259, in 
dispatch_bytecode
||     res = meth(oparg, next_instr)
||   File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 558, in 
RAISE_VARARGS
||     raise operror
Traceback (application-level):
  File "<inline>", line 1 in <module>
    raise ValueError
(application-level) ValueError
>>>> 

One comes from record_intepreter_traceback in main.py, the other from 
record_interpreter_traceback in executioncontext.py. Is one redundant?

----------
messages: 5457
nosy: bdk, pypy-issue
priority: bug
status: unread
title: pyinteractive.py -v prints duplicate interpreter-level tracebacks

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue1425>
________________________________________


More information about the pypy-issue mailing list