Jack Jansen wrote:

And, more serious, there's another example for the 2.2b1 release that I found just friday (so this bug is going to stay in MacPython 2.2b1, I'm afraid): importing packages from frozen programs is broken.

There was a moderately simple fix to import.c, to test that submodules of frozen modules were also frozen, and not picked up from the filesystem. Unfortunately whoever did the patch wasn't aware that MacPython frozen modules work different, and hence broke it.

I remember seeing that, and meaning to look into it but forgot. I think it's a highly questionable fix, not only for MacPython: I'm not sure if this still allows C extensions as submodules in frozen apps. Just

Jack Jansen wrote:

And, more serious, there's another example for the 2.2b1 release that I found just friday (so this bug is going to stay in MacPython 2.2b1, I'm afraid): importing packages from frozen programs is broken.

There was a moderately simple fix to import.c, to test that submodules of frozen modules were also frozen, and not picked up from the filesystem. Unfortunately whoever did the patch wasn't aware that MacPython frozen modules work different, and hence broke it.

I remember seeing that, and meaning to look into it but forgot. I think it's a highly questionable fix, not only for MacPython: I'm not sure if this still allows C extensions as submodules in frozen apps. Just