[issue7361] Strange importlib error during test_multiprocessing failure

Brett Cannon added the comment: Huh. I wonder how importlib is ending up being the implementation of import then? Guess I also need to double-check everything is still cleaning itself up properly. -- ___ Python tracker

[issue7361] Strange importlib error during test_multiprocessing failure

R. David Murray added the comment: This was on a buildbot, and regrtest -j isn't used there, but in any case it wouldn't affect importlib as far as I know. From the traceback it looks like multiprocessing is just doing an import. -- ___ Python track

[issue7361] Strange importlib error during test_multiprocessing failure

Brett Cannon added the comment: And it looks like the error was triggered from a malformed .pyc file that was truncated. Guess I need to be more careful with that possibility. =) -- ___ Python tracker

[issue7361] Strange importlib error during test_multiprocessing failure

Brett Cannon added the comment: I will obviously have a look, but why the heck is test_multiprocessing calling importlib? Is it meant to do that? Or is this part of the -j flag for regrtest? -- assignee: -> brett.cannon ___ Python tracker

[issue7361] Strange importlib error during test_multiprocessing failure

New submission from R. David Murray : One of the buildbots suffered a test_multiprocessing failure, which itself is not such an unusual thing. But the error that was subsequently thrown looks like it might point to a place where importlib's error handling could be improved. The error that was t