Nick Coghlan added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25268> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
