[issue14439] RunModule(): display the traceback on failure

Nick Coghlan added the comment: Never mind, I just looked at your patch and better understand what you're wanting to improve (i.e. diagnosing problems with bootstrapping runpy itself, not the errors that occur after runpy has already been found). However, your proposed solution is questionabl

[issue14439] RunModule(): display the traceback on failure

Nick Coghlan added the comment: Huh? Demonstration please, as the -m switch absolutely does display tracebacks when the call fails: $ python -m timeit -s "raise RuntimeError" Traceback (most recent call last): File "/usr/lib64/python2.7/timeit.py", line 298, in main x = t.timeit(number)

[issue14439] RunModule(): display the traceback on failure

Changes by Antoine Pitrou : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14439] RunModule(): display the traceback on failure

New submission from STINNER Victor : "python -m module" calls the C RunModule() function. If this function fails, the traceback is not displayed and so it is difficult to understand why the problem is. I propose to display the traceback when this function fails, as it is already done on runpy