[issue7361] importlib not checking bytecode length

2010-02-07 Thread Brett Cannon
Brett Cannon added the comment: A quick check of things shows that a totally empty file, a missing timestamp, or no marshalled code triggers the use of source. I still need to check what happens when the magic number is truncated by a byte or so along with the timestamp. Any screw-up with th

[issue7361] importlib not checking bytecode length

2010-02-07 Thread Brett Cannon
Brett Cannon added the comment: issue #7875 brought up the original failure that caused the creation of this bug again and led to me finally diagnosing the problem. -- ___ Python tracker __

[issue7361] importlib not checking bytecode length

2010-02-03 Thread Brett Cannon
Brett Cannon added the comment: I can't reproduce the failure as running test_multiprocessing and then test_importlib does not show any left over stuff in the interpreter what would lead to importlib being used for __import__. But as the IndexError part is a valid issue I am renaming the issu