[issue15031] Split .pyc parsing from module loading

[Brett Cannon]

Brett Cannon added the comment:

In order to have exceptions that have messages like "bad magic number in module" there would need to be a technically unneeded fullname parameter. People cool with that? I personally dislike having info passed in just for error reporting, but in this case import exceptions typically try to clarify what actually caused the issue by naming the module since you can end up with deep implicit module chains.

The other stuff related to bytecode paths are just for verbose logging or for setting path on ImportError, both of which can be worked around.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15031>
_______________________________________