You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Python itself displays the stacktrace for BdbQuit. Should we also display it, possibly with any test summary?
-> print("hello18")
(Pdb) q
Traceback (most recent call last):
File "test_pdb.py", line 17, in <module>
test_1()
File "test_pdb.py", line 8, in test_1
print("hello18")
File "test_pdb.py", line 8, in test_1
print("hello18")
File "…/pyenv/3.6.6/lib/python3.6/bdb.py", line 51, in trace_dispatch
return self.dispatch_line(frame)
File "…/pyenv/3.6.6/lib/python3.6/bdb.py", line 70, in dispatch_line
if self.quitting: raise BdbQuit
bdb.BdbQuit
When using Exit or Interrupted it will not display any of those.
should there be an option on Exit (similar to returncode) to display
traceback and test summary, as with a failed test?
An option (hack?) might be to raise Failed (that's how BdbQuit gets up
handled currently (in master)), and set a flag on the session to stop? (basically exitfirst then)
would Interrupted (from/on Session) be more appropriate here than Exit?
should there be an option for this behavior(s)?
After all I like that currently on features it exits rather cleanly with
"Exiting debugger", without stacktrace and "short test summary info" etc.
The text was updated successfully, but these errors were encountered:
Python itself displays the stacktrace for BdbQuit. Should we also display it, possibly with any test summary?
When using
Exit
orInterrupted
it will not display any of those.Exit
(similar toreturncode
) to displaytraceback and test summary, as with a failed test?
An option (hack?) might be to raise
Failed
(that's howBdbQuit
gets uphandled currently (in master)), and set a flag on the session to stop? (basically exitfirst then)
would
Interrupted
(from/onSession
) be more appropriate here thanExit
?should there be an option for this behavior(s)?
After all I like that currently on features it exits rather cleanly with
"Exiting debugger", without stacktrace and "short test summary info" etc.
The text was updated successfully, but these errors were encountered: