On Tuesday, December 06, 2011 10:03:32 AM Hartmut Goebel wrote: > Am 05.12.2011 12:39, schrieb Sebastian Hilbert: > > Anyway I have since commented it out in rthooks.dat (no idea if this > > might break other things). > > Well, this is not a good idea. Runtime-hooks are not for fun, but they > exist because they are required. > > If you cut off parts of you app, you do not need to wonder why it is > failing. > :-) I did this as a test because I found a reference in the bugtracker.
> You need to find out, which part of you app is requiring pywin32 and why > it is not found. That is what I thought. Ok. Different from what upstream initially said there is some reference to pyiwin32 I just searched the source tree and found from win32com import client as dde_client Since it is wrapped in a try, except statement it would not be critical to leave it out for the inital packaging effort. > > > ImportError: No module named mxDateTime > > If you look the the traceback, you will find out what is > missing: mx/DateTime/mxDateTime/mxDateTime.pyd In the output directory of the exe I see a file mx.DateTime.mxDateTime.mxDateTime.pyd That made me think it is picked up properly. What exactly would I have to look for in the outPYZ1.pyz when trying to find out if it is properly included or not ? Regards, Sebastian -- 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.
