Message1895

this issue is already fixed (just fixed today, actually) by the new zipimporter. trunk r3461, pre new zipimporter does:

pjenvey@golgo13-wireless:~/Desktop/Downloads/importfromjar$ jythont start_ok_fromdir.py 
RUN-OK
pjenvey@golgo13-wireless:~/Desktop/Downloads/importfromjar$ jythont start_ok_fromzip_source.py 
RUN-OK
pjenvey@golgo13-wireless:~/Desktop/Downloads/importfromjar$ jythont start_BAD_fromzip_nosource.py 
Traceback (innermost last):
  File "start_BAD_fromzip_nosource.py", line 5, in ?
ImportError: no module named mod1

trunk HEAD, r3464 (with new zipimporter):

pjenvey@golgo13-wireless:~/Desktop/Downloads/importfromjar$ jythont start_ok_fromdir.py 
RUN-OK
pjenvey@golgo13-wireless:~/Desktop/Downloads/importfromjar$ jythont start_ok_fromzip_source.py 
RUN-OK
pjenvey@golgo13-wireless:~/Desktop/Downloads/importfromjar$ jythont start_BAD_fromzip_nosource.py 
RUN1

RUN1 is displayed because the compiled $py.class in both zips actually prints RUN1, which is  a mismatch with the associated .py file that prints RUN-OK.

RUN1 isn't displayed for the zip with source because the uncompiled .py file in it actually has a later modification time than the compiled version

Thanks for logging this with the extensive test! Although the issue was already fixed, this was a nice little test for the brand new zipimporter that hasn't had much real world use yet