[issue16217] Tracebacks are unnecessarily verbose when using 'python -m'
Nick Coghlan
report at bugs.python.org
Sat Oct 13 16:52:32 CEST 2012
Nick Coghlan added the comment:
Agreed. We do have a mechanism in place to deal with this specifically for importlib in 3.3 (which is why the first traceback is cleaner, although it's not triggering in the SyntaxError case for some reason), but it makes sense to hide the noise from runpy as well.
Flagging 3.3 for the moment, but if the change is too intrusive it will end up being 3.4 only.
----------
assignee: -> ncoghlan
nosy: +brett.cannon
versions: +Python 3.3, Python 3.4
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16217>
_______________________________________
More information about the Python-bugs-list
mailing list