[Image-SIG] PIL and py2exe

Sean Curtis scurtis at cs.utah.edu
Tue Aug 16 16:49:17 CEST 2005

the initialization of PIL does two things that are banging heads with py2exe:

    1) It always imported Tk "just in case".  Even if I'm not using Tk, Tk is imported.  This causes py2exe to load everything in Tk causing my install to get ridiculously huge.  Is there any way around this?

    2) The file format modules are imported on the sly using the __import__ function and constructing the module names at runtime (or at least at compile time.)  Because of this, py2exe doesn't recognize module dependencies and I get a distribution with no file plugins (and thus, the ability to read NOTHING.)

    My gut feeling is that the answer for 1 is what's being done in 2 and the answer to 2 is what's being done in 1.  Is there any around these things other than my hacking my own install of PIL?


Sean Curtis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/image-sig/attachments/20050816/e4d46733/attachment.html

More information about the Image-SIG mailing list