I think I see how the run time hooks work; if you want, I'll attach an updated rthooks.dat and appropriate run time hook for PIL that should (!) take care of this problem.
On Mon, Nov 21, 2011 at 3:16 PM, Hartmut Goebel <[email protected]>wrote: > Am 21.11.2011 20:34, schrieb Daniel Hyams: > > 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. > > Yes, I think, this is the only solution. > > > 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). > > It should be possible to exclude unused plugins. Let's solve this later > by publishing a recipe :-) > > -- > 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.
