I don't know; I would have to instrument PIL's Image.py a little more to see what it thinks "directories" is, in the code that I posted in the first post here.
Perhaps a solution to this is to have a run-time hook that always imports all of the modules in the hiddenimports list. If that happens, that makes PIL's run-time import machinery (again, posted in the first thread) not needed, since all of its plugins have already been registered. The downside of doing this is that if a user is only working with PNG's (for example), they have to pay for having *every* plugin imported and in memory. I do not see that as a big cost, however (just my opinion). I do not know anything about the run-time hooks myself...but I don't think that this would be hard to do. The only rub is that the exact list of plugins to be imported at run-time is only known at the time pyinstaller is used to build, rather than always being known. On Mon, Nov 21, 2011 at 2:25 PM, Hartmut Goebel <[email protected]>wrote: > Am 21.11.2011 01:04, schrieb Daniel Hyams: > > Note that the test will pass, if you have PIL installed, because > > imports "leak" through to your installed python. [To prove this, > > stick a print statement at the top of > > Huh? How can this leak if sys.path is only _MEIPASS-dir? > > -- > Schönen Gruß - Regards > Hartmut Goebel > Dipl.-Informatiker (univ.), CISSP, CSSLP > > Goebel Consult > Spezialist für IT-Sicherheit in komplexen Umgebungen > http://www.goebel-consult.de > > Monatliche Kolumne: http://www.cissp-gefluester.de/ > Goebel Consult ist Mitglied bei http://www.7-it.de > > > -- Daniel Hyams [email protected] -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
