On 04/11/14 11:52, Michael Sverdlik wrote:
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..)
In the past when I had some imports that were not being picked up this
way that I did/could not have directly imported I found that
pyInstaller/py2exe would find them if I included in the module, if
False: import some_module - a bit of a hack but it worked.
Gadget/Steve
--
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.
