On Fri, 2008-02-08 at 16:43 +0100, Masaru wrote: > >> incursio wrote: > >>> nop... the freeze process ends normally and the generated binary > >>> doesnt give any traceback error. The program just doesnt do what I > >>> want but it doesnt go down it just keeps runing. > > > > > Heyho, > > the problem is part of a process, renaming the imported pyd modules > by pyinstaller analyzing/buikd/or whatever procedures. > > I don't know where, but pyinstaller stores the: > <python>\Lib\site-packages\pyHook\_cpyHook.pyd > > ... in the single directory process finally as following file: > <dist>\pyHook._cpyhook.pyd > > ... instead of (which pyHook needs actually): > <dist>\_cpyHook.pyd > > If you make a single directory (not a single file) build, you > can fix this realy simple by renaming the "pytHook._cpyHook.pyd" > into "_cpyHook.pyd" in the dist-directory. > > But in single file build, there must be a better workaraound, hook > or what else ;) > > Here can Giovanni better help than I.
Well, _cpyHook is within the pyHook directory, so the actual decorated name is "pytHook._cpyHook", hence the pyd filename. [I'll notice that pyHook will not work with the new absolute imports in Python 2.6 because it uses "import _cpyHook" from within the package]. So the problem must be related to the runtime import manager which is not able to resolve the import, for some reason. It's really weird that it doesn't result in a simple ImportError, though: I would expect that in case the import wasn't resolved. I'll have to debug it more accurately under Windows though. -- Giovanni Bajo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
