New submission from Cal Leeming:
Originally posted here:
http://stackoverflow.com/q/33873243/1267398
The problem is caused by this line:
# For -m switch, just display the exception
info = str(exc)
Caused by the following commit in 2008;
https://mail.python.org/pipermail/python-checkins/2008-February/066256.html
The commit states;
"Try to make command line error messages from runpy easier to understand (and
suppress traceback cruft from the implicitly invoked runpy machinery)"
However by suppressing the traceback it's now impossible to debug what caused
the error when running with `runpy` without wrapping the entire `__init__.py`
with your own try/except statement.
I'd like to propose either displaying the full traceback by default, or adding
a CLI option to enable it at runtime. The fact that it only suppresses *some*
tracebacks and not all is a flawed approach surely?
Thoughts?
----------
components: Interpreter Core
messages: 255169
nosy: ncoghlan, sleepycal
priority: normal
severity: normal
status: open
title: runpy hides traceback for some exceptions
type: behavior
versions: Python 3.4
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25708>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
