Oh, ok good to know I wasn't losing my mind for nothing :-) Is it open on Github or would you like me to report it?
Is there a known workaround for this? Maybe in dev branch or any other smart way to bypass this? (My only idea is to scan each module for *.py and add these to the scripts list in the Analysis phase..) On Tuesday, November 4, 2014 1:48:34 PM UTC+2, Hartmut Goebel wrote: > > Am 04.11.2014 um 12:41 schrieb Michael Sverdlik: > > I thought that hiddenimport behaviour is the same as if I had explicit > import statement in my script? > > > Yes, it is. Both ways use the same code. > > -- > Schönen Gruß > Hartmut Goebel > Dipl.-Informatiker (univ), CISSP, CSSLP > Information Security Management, Security Governance, Secure Software > Development > > Goebel Consult, Landshut > http://www.goebel-consult.de > > Blog: > http://www.goebel-consult.de/blog/in-need-for-an-enhanced-git-url-scheme > Kolumne: http://www.cissp-gefluester.de/2010-08-scheingefechte-um-rim > > Goebel Consult ist Mitglied bei http://www.7-it.de/ > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
