Brett Cannon added the comment: So the more I think about this, the more I'm willing to do this in Python 3.4. First, though, the docs would need to be updated in importlib to distinguish between bytecode and byte-compiled files.
>From there, I think importlib.abc.SourceLoader.parse_byte_compiled_file(data) >could exist. It would be a classmethod so people can call it directly if they >really want. It would verify the magic number, and if that's good, return a >dict that can be directly compared against what path_stats() returns plus the >bytecode for the module. This should properly shield the format of bytecode >from users while still providing an API people can rely on. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15031> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
