[issue31300] Traceback prints different code than the running module

2017-08-29 Thread R. David Murray
R. David Murray added the comment: This is a duplicate of issue 8087, which contains quite a bit of discussion of the subtleties of the issue. -- nosy: +r.david.murray resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Unupdated source file in

[issue31300] Traceback prints different code than the running module

2017-08-29 Thread Aigars Mahinovs
New submission from Aigars Mahinovs: If you run a longer running Python program, then change the Python module that it loaded on disk and then cause a traceback to happen in the code in that module, then the traceback may be nonsensical as it will reference line numbers from the module in