This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients brett.cannon, eric.snow, lemburg, ncoghlan
Date 2016-09-24.17:15:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474737358.53.0.766688466376.issue25268@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with Marc-Andrew that it's hard to do anything more useful here than "-r" already does, as we can assume the source code won't be available on the target machine - it's the equivalent of having C/C++ debugging symbols available for C/C++ traceback generation.

It may still be worth doing specifically for the sake of _frozen_importlib (as that usually *does* have the importlib._bootstrap code available at runtime), but I think it would be pretty specific to that particular case.

A more generally applicable feature would be a utility to take a traceback of the form created by -r (as shown by Marc-Andre above), and converting that back to a full traceback given a directory structure that matched the layout of the frozen modules.
History
Date User Action Args
2016-09-24 17:15:58ncoghlansetrecipients: + ncoghlan, lemburg, brett.cannon, eric.snow
2016-09-24 17:15:58ncoghlansetmessageid: <1474737358.53.0.766688466376.issue25268@psf.upfronthosting.co.za>
2016-09-24 17:15:58ncoghlanlinkissue25268 messages
2016-09-24 17:15:57ncoghlancreate