On Monday, December 05, 2011 12:09:03 PM Sebastian Hilbert wrote:
> Hi all,
>
> Thanks for your work on pyinstaller. I have had good results with
> pyinstaller-1-4-rc1 and python 2.5 for some time now.
>
> Due to upstream changes in GNUmed 1.1.6 which I am trying to package I had
> to move to pyinstaller 1.5.1 and upgrade python along the way. I upgraded
> to python 2.7.
>
> Running the newly created build environment did not produce a working
> executable as it had done before.
>
> When setting the debug flag in pyinstaller I noticed that it is now
> required to install pywin32. I downloaded and installed the corresponding
> version for python 2.7 from sf.net.
>
> in a terminal in Windows XP I can successfully issue command such as
> import win32api.
>
I might add that as far as I know GNUmed does not make use of win32api.
Anyway I have since commented it out in rthooks.dat (no idea if this might
break other things).
Rebuilding and running the exe takes me further and fails with the message.
#########
import datetime # builtin
*** You don't have the (right) mxDateTime binaries installed !
.========================================================
| Unhandled exception caught !
| Type : <type 'exceptions.ImportError'>
| Value: No module named mxDateTime
`========================================================
Traceback (most recent call last):
File "<string>", line 524, in <module>
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 477, in importHook
mod = self.doimport(nm, ctx, ctx+'.'+nm)
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 521, in doimport
exec co in mod.__dict__
File "C:\workplace\gnumed-
client.1.1.6\build\pyi.win32\setup\outPYZ1.pyz/Gnume
d.pycommon.gmDateTime", line 50, in <module>
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 436, in importHook
mod = _self_doimport(nm, ctx, fqname)
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 521, in doimport
exec co in mod.__dict__
File "C:\workplace\gnumed-
client.1.1.6\build\pyi.win32\setup\outPYZ1.pyz/mx.Da
teTime", line 8, in <module>
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 436, in importHook
mod = _self_doimport(nm, ctx, fqname)
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 521, in doimport
exec co in mod.__dict__
File "C:\workplace\gnumed-
client.1.1.6\build\pyi.win32\setup\outPYZ1.pyz/mx.Da
teTime.DateTime", line 9, in <module>
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 436, in importHook
mod = _self_doimport(nm, ctx, fqname)
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 521, in doimport
exec co in mod.__dict__
File "C:\workplace\gnumed-
client.1.1.6\build\pyi.win32\setup\outPYZ1.pyz/mx.Da
teTime.mxDateTime", line 13, in <module>
ImportError: No module named mxDateTime
RC: -1 from gnumed
OK.
#####################################
strangely enough when looking at outPYZ1.pyz with Archiveviewer I can see
references like this
'mailcap': (False, 1109323L, 3304),
'mimetools': (False, 3172499L, 3471),
'mimetypes': (False, 2941840L, 6583),
'mx': (True, 462989L, 488),
'mx.DateTime': (True, 2114008L, 964),
'mx.DateTime.ARPA': (False, 287580L, 3034),
'mx.DateTime.DateTime': (False, 2950027L, 10221),
'mx.DateTime.ISO': (False, 2829724L, 3294),
'mx.DateTime.Parser': (False, 2262579L, 12873),
'mx.DateTime.Timezone': (False, 3109675L, 1832),
'mx.DateTime.mxDateTime': (True, 678956L, 684),
'mx.Misc': (True, 1825054L, 126),
'mx.Misc.LazyModule': (False, 3177741L, 1790),
'netbios': (False, 3014783L, 3688),
'new': (False, 292016L, 538),
'ntpath': (False, 282273L, 5307),
'nturl2path': (False, 3709L, 967),
'numbers': (False, 649365L, 3648),
and in the directory where the exe resides I can see a
mx.DateTime.mxDateTime.mxDateTime.pyd
If it helps I could zip up the relevant files and provide it for testing.
Any help is appreciated.
Sebatian Hilbert
--
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.