From: Gordon S. <gsc...@gm...> - 2005-09-07 21:24:31
|
>=20 >=20 > >>Yes - this is a pretty strange effect of a bug that loaded extensions > >>more than once. Which led to the effect that the > >>except (ImportError, win32api.error): > >>line in win32serviceutil.py didn't catch the error. I've fixed that in > >>CVS, and will release 0.6.2 soon. > >> > >>Thomas I just downloaded 0.6.2 and started playing with it. I'm seeing a differen= t=20 problem now when building a single file executable. I am using the mxODBC= =20 module for database access and it is failing to locate the mxDateTime=20 package.=20 It looks like it did not translate an import string into a file path. It i= s=20 looking for=20 collect-2.4\mx.DateTime.mxDateTime\mxDateTime.pyd instead of collect-2.4\mx\DateTime\mxDateTime\mxDateTime.pyd ? Here is the output at the end of a compilation attempt *** copy extensions *** copying C:\Python\Python24\DLLs\_socket.pyd ->=20 C:\dev\WCMS\image_processing\Medi aUnzipper\build\bdist.win32\winexe\collect-2.4 copying C:\Python\Python24\DLLs\bz2.pyd ->=20 C:\dev\WCMS\image_processing\MediaUnz ipper\build\bdist.win32\winexe\collect-2.4 copying C:\Python\Python24\DLLs\pyexpat.pyd ->=20 C:\dev\WCMS\image_processing\Medi aUnzipper\build\bdist.win32\winexe\collect-2.4 copying C:\Python\Python24\DLLs\unicodedata.pyd ->=20 C:\dev\WCMS\image_processing\ MediaUnzipper\build\bdist.win32\winexe\collect-2.4 copying C:\Python\Python24\DLLs\zlib.pyd ->=20 C:\dev\WCMS\image_processing\MediaUn zipper\build\bdist.win32\winexe\collect-2.4 copying=20 C:\Python\Python24\lib\site-packages\mx\DateTime\mxDateTime\mxDateTime.p yd ->=20 C:\dev\WCMS\image_processing\MediaUnzipper\build\bdist.win32\winexe\collec t-2.4\mx.DateTime.mxDateTime error:=20 C:\dev\WCMS\image_processing\MediaUnzipper\build\bdist.win32\winexe\colle ct-2.4\mx.DateTime.mxDateTime\mxDateTime.pyd: No such file or directory |