[issue14439] Easier error diagnosis when bootstrapping the runpy module in main

STINNER Victor added the comment: Testing the patch manually is simple: add anything wrong in runpy.py and run "python -m base64". Output: --- Could not import runpy module --- Output with the patch: --- Could not import runpy module Traceback (most recent call last): File "/home/haypo/prog/

[issue14439] Easier error diagnosis when bootstrapping the runpy module in main

Roundup Robot added the comment: New changeset 39b9b05c3085 by Victor Stinner in branch 'default': Close #14439: Python now prints the traceback on runpy failure at startup. http://hg.python.org/cpython/rev/39b9b05c3085 -- nosy: +python-dev resolution: -> fixed stage: -> committed/reje

[issue14439] Easier error diagnosis when bootstrapping the runpy module in main

Nick Coghlan added the comment: Taking a closer look at the four affected cases, I've changed my mind - the patch looks reasonable, go ahead and add it (as the new output actually still makes sense in the RunMainFromImporter case) However, additional test cases should be added to test_cmd_lin

[issue14439] Easier error diagnosis when bootstrapping the runpy module in main

Changes by Nick Coghlan : -- title: RunModule(): display the traceback on failure -> Easier error diagnosis when bootstrapping the runpy module in main ___ Python tracker ___ __