Am Mittwoch, den 28.12.2011, 13:56 +0100 schrieb Hartmut Goebel: > Hi, > > welcome to PyInstaller.
Hi, and thanks for the welcome and reply! > [...] > So you already did find your way to the hooks :-) Did you wollow the > instructions at > <http://www.pyinstaller.org/wiki/HowtoReportBugs#Beforesubmittingareport:Makesureeverythingispackaged> > > to find out why your stuff is missing? Ep. logdict*.log and warn*.txt > should help you. I've taken a look at those, but I think my problem is quite clear -- Gourmet.exe issues [...] File ".\build\pyi.win32\Gourmet \outPYZ1.pyz/gourmet.defaults.defaults", line 27, in <module> File "C:\Python27\Tools\pyinstaller-1.5.1\iu.py", line 455, in importHook raise ImportError, "No module named %s" % fqname ImportError: No module named defaults_en What's not so clear if the solution: AFAICS, the proper way to fix this sort of hidden imports is to add a hook. I've experimented with a lot of different names for the hooks that seemed to make sense (e.g. hooks-gourmet.defaults.defaults.py or hooks-gourmet.defaults.defaults.lang.py), but no success so far. gourmet.defaults.defaults_en isn't in Gourmet.exe's outPYZ1.pyz archive, either; the only modules starting with gourmet.defaults are 'gourmet.defaults': (True, 2511381L, 141), 'gourmet.defaults.defaults': (False, 1515441L, 1469), I've added the warnGourmet.txt and logdict*.txt files now to the git repo (pyinstaller branch again, of course), so maybe you (or someone else) can point me to what I'm missing... > In your spec-file I discovered there are absolute, user and system > dependant paths (C:\\Users\\Bernie\\workspace\). You should replace > these by independent (and relative) paths. Hm, I removed those with a commit before I wrote my last mail -- see http://grecipe-manager.git.sourceforge.net/git/gitweb.cgi?p=grecipe-manager/grecipe-manager;a=blob;f=windows/Gourmet.spec;h=b5b35e110ef1ab1115a3c5a76650ac42bcbab6fc;hb=refs/heads/pyinstaller Could it be that you used a revision that dates before that commit? > Further remarks: Gourmet.pyw imports a lot of stuff which is not > necessary to be imported. PyInstaller should resolve most of it > automatically. See the first lines and the encoding.* stuff. If you are > going to keep it, I suggest order the imports according to PEP 8 and > keep line length below 80 chars. That's part of my heritage as Gourmet's Windows maintainer ;-) but I'd like to tackle that separately after I've successfully built a working Gourmet.exe, unless it's absolutely necessary. Anyway, it's pretty damn cool that I'm now able to do this type of diagnosing from within Linux, using pyinstaller from within Wine... No more need to reboot like I had to with py2exe. (BTW, the error was the same under Windows, so that doesn't seem to make a difference.) > I just added Gourmet Recipe Manager to > http://www.pyinstaller.org/wiki/ProjectsUsingPyInstaller. Okay? Okay if I really can get it to work ;-) Regards Bernhard -- 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.
