From: Tim B. <ti...@tb...> - 2005-10-19 08:08:17
|
Hi, Still tryin' to freeze my wxmpl matplotlib application.... sigh. This is wxpython + wxmpl + matplotlib. This has turned into one hell of a fight - BUT I think I am about to win. You have to keep the faith :-} Name the py2exe issue with freezing matplotlib / wxmpl and I have been there fought that. I have slayed many dragons... I now have a problem that has been asked before on this list. I have tried the answer that was offered- it didnt help. I think I am in a postion to ask a simple solid question... When I run my application I see this.... Fatal Python error: Call to API function without first calling import_libnumarray() in Src\_convmodule.c This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. I added import numarray all over the place... a previous post suggested that maybe Wxpython was calling numarray before I was... no I dont think wxpython and numarray ever need each other. To help prove this I changed my application to this: (a boa app - so this code occurs early in execution but not before wxpython has been used... def __init__(self, parent): import numarray import numarray.numarrayall # desperate attempt to stop error api call without first calling import_libnumarray self._init_ctrls(parent) # init wxpython controls print numarray.__version__ and bang my application no longer runs. If I comment out this print line, the application runs perfectly except when you click the button to draw the graph. Then you get the same error message as above. BTW in the development environments - application works fine - and that's because the development environs are loading the modules from the python installation - is my call... In my library file you can see that numarray is definitely included - it's there. So my question is: Q: How do you force the loading (not the inclusion) of the nummary module? Or how do you get import_libnumarray to run? Can some one tell me more about the mechanism python uses to load the modules.. What triggers the load call? Where? I know I am close. Rest of the application is 95% finished. Customer loves it. 2 week delay coz I cant freeze the @#$@$%@ thing. BTW kudos to py2exe developers and maintainers - as I learn more about the challenges in identifying the modules and the packaging of them etc - I appreciate it. This is not a sucking up effort to get an answer - but if it helps.... :-} thanks PS I have cross posted this to matploblib and py2exe lists - I am desperate! -- Tim Burgess IT Consultant RedHat Certified Engineer TBITC Pty Ltd Professional Computer Support for Business ti...@tb... Mobile 0422 942 972 Office 85 662 016 http://www.tbitc.com |
From: Rob M. <rob...@in...> - 2005-10-19 08:46:55
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Suddenly I feel less alone.<br> <br> .<br> I'm engaged in exactly the same process right now, I've tried moving the whole of numarray into the dist a dir out of sheer desperation....but no go- my traceback looks like this.....<br> <br> Traceback (most recent call last):<br> Traceback (most recent call last):<br> File "HacGui.py", line 21, in ?<br> File "activity.pyc", line 17, in ?<br> File "matplotlib\axes.pyc", line 5, in ?<br> File "C:\DOCUME~1\ROBMAR~1\REPO\Hydra2\hydra\admin\client\HAC\build\dist\__init__.pyc", line 95, in ?<br> <br> ImportError: No module named random_array<br> <br> As soon as I remove numarray fropm the dist dir this resolves to <br> <br> <br> Fatal Python error: Call to API function without first calling import_libnumarray() in Src\_convmodule.c<br> <br> I came across a post yesterday <a class="moz-txt-link-freetext" href="http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/2852995">http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/2852995</a> that suggests that it's possible to <br> 'force' the whole of numarray into an app. I'd like to know how though<br> <br> <b>Russell E. Owen wrote: <span class="mail_quotation">> If I convert my python code to an application (Windows via py2exe or Mac </span><span class="mail_quotation">> via bundlebuilder) it fails with the following error:</span> <span class="mail_quotation">> </span><span class="mail_quotation">> Fatal Python error: Call to API function without first calling </span><span class="mail_quotation">> import_libnumarray() in Src/_convmodule.c</span> <span class="mail_quotation">> </span><span class="mail_quotation">> </span>This currently (1.3.3) happens when a numarray API function is called before the API is successfully initialized. Although the message was intended as an aid to extension writers, in this case numarray is failing to import altogether. At one point numarray had a fatal error for import failures but I removed it at someone's request. I've restored it because I think it's most commonly fatal anyway and removing the message just obfuscated the problem. The non-fatal behavior is now in the _import_libnumarray() macro. <span class="mail_quotation">> I can force *all* of numarray into the application, which avoids the </span><span class="mail_quotation">> </span><span class="mail_quotation">> </span> This is what you need to do. It should be possible to factor out (or not explicitly list) numarray's Packages, but core numarray is not meant to be distributed in pieces. The many type-specific extensions were only added to work around a compiler problem, not to lighten binary distributions. .</b> <br> <br> <br> <br> <br> ('.', glob.glob(r'C:\PROGRA~1\Python24\share\MATPLO~1\matplotlibrc')),<br> ('.', glob.glob(r'C:\PROGRA~1\Python24\Lib\SITE-P~1\numarray\*.py')), <br> <br> .....seems to take care of an earlier error ( can't find matplotlibrc file) <br> <br> You have my complete empathy on this problem. In the event I come up with some sort of magic bullet, I'll mail you ASAP.<br> <br> Have fun <span class="moz-smiley-s1"><span> :-) </span></span><br> <br> Rob M.<br> <br> <br> <br> Tim Burgess wrote: <blockquote cite="mid...@tb..." type="cite">Hi, <br> Still tryin' to freeze my wxmpl matplotlib application.... sigh. <br> <br> This is wxpython + wxmpl + matplotlib. This has turned into one hell of a fight - BUT I think I am about to win. You have to keep the faith :-} <br> <br> Name the py2exe issue with freezing matplotlib / wxmpl and I have been there fought that. I have slayed many dragons... <br> <br> I now have a problem that has been asked before on this list. I have tried the answer that was offered- it didnt help. I think I am in a postion to ask a simple solid question... <br> <br> When I run my application I see this.... <br> <br> Fatal Python error: Call to API function without first calling import_libnumarray() in Src\_convmodule.c <br> <br> This application has requested the Runtime to terminate it in an unusual way. <br> Please contact the application's support team for more information. <br> <br> I added import numarray all over the place... a previous post suggested that maybe Wxpython was calling numarray before I was... no I dont think wxpython and numarray ever need each other. <br> <br> To help prove this I changed my application to this: (a boa app - so this code occurs early in execution but not before wxpython has been used... <br> <br> def __init__(self, parent): <br> <br> import numarray <br> import numarray.numarrayall # desperate attempt to stop error api call without first calling import_libnumarray <br> self._init_ctrls(parent) # init wxpython controls <br> <br> print numarray.__version__ <br> <br> and bang my application no longer runs. If I comment out this print line, the application runs perfectly except when you click the button to draw the graph. Then you get the same error message as above. <br> <br> BTW in the development environments - application works fine - and that's because the development environs are loading the modules from the python installation - is my call... <br> <br> In my library file you can see that numarray is definitely included - it's there. <br> <br> So my question is: <br> Q: How do you force the loading (not the inclusion) of the nummary module? Or how do you get import_libnumarray to run? <br> <br> Can some one tell me more about the mechanism python uses to load the modules.. What triggers the load call? Where? <br> <br> I know I am close. Rest of the application is 95% finished. Customer loves it. 2 week delay coz I cant freeze the @#$@$%@ thing. <br> <br> BTW kudos to py2exe developers and maintainers - as I learn more about the challenges in identifying the modules and the packaging of them etc - I appreciate it. This is not a sucking up effort to get an answer - but if it helps.... :-} <br> <br> thanks <br> <br> PS I have cross posted this to matploblib and py2exe lists - I am desperate! <br> <br> </blockquote> <br> <pre class="moz-signature" cols="72">-- O__ _/`.\ `=( ' </pre> </body> </html> |
From: Werner F. B. <wer...@fr...> - 2005-10-19 10:02:42
|
Hi Rob, Rob Marino wrote: > Suddenly I feel less alone. > > .. > I'm engaged in exactly the same process right now, I've tried moving the > whole of numarray into the dist a dir out of sheer desperation....but > no go- my traceback looks like this..... > > Traceback (most recent call last): > Traceback (most recent call last): > File "HacGui.py", line 21, in ? > File "activity.pyc", line 17, in ? > File "matplotlib\axes.pyc", line 5, in ? > File > "C:\DOCUME~1\ROBMAR~1\REPO\Hydra2\hydra\admin\client\HAC\build\dist\__init__.pyc", > line 95, in ? > > ImportError: No module named random_array If I remember correctly I had solved that by including "matplotlib.numerix" into the packages to force include in py2exe. "packages": ["encodings", "kinterbasdb", "pytz", "matplotlib.numerix"], See you Werner > > As soon as I remove numarray fropm the dist dir this resolves to > > > Fatal Python error: Call to API function without first calling > import_libnumarray() in Src\_convmodule.c > > I came across a post yesterday > http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/2852995 > that suggests that it's possible to > 'force' the whole of numarray into an app. I'd like to know how though > > *Russell E. Owen wrote: > If I convert my python code to an application > (Windows via py2exe or Mac > via bundlebuilder) it fails with the > following error: > > Fatal Python error: Call to API function without > first calling > import_libnumarray() in Src/_convmodule.c > > This > currently (1.3.3) happens when a numarray API function is called before > the API is successfully initialized. Although the message was intended > as an aid to extension writers, in this case numarray is failing to > import altogether. At one point numarray had a fatal error for import > failures but I removed it at someone's request. I've restored it because > I think it's most commonly fatal anyway and removing the message just > obfuscated the problem. The non-fatal behavior is now in the > _import_libnumarray() macro. > I can force *all* of numarray into the > application, which avoids the > > This is what you need to do. It should > be possible to factor out (or not explicitly list) numarray's Packages, > but core numarray is not meant to be distributed in pieces. The many > type-specific extensions were only added to work around a compiler > problem, not to lighten binary distributions. ..* > > > > > ('.', > glob.glob(r'C:\PROGRA~1\Python24\share\MATPLO~1\matplotlibrc')), > ('.', > glob.glob(r'C:\PROGRA~1\Python24\Lib\SITE-P~1\numarray\*.py')), > > ......seems to take care of an earlier error ( can't find matplotlibrc > file) > > You have my complete empathy on this problem. In the event I come up > with some sort of magic bullet, I'll mail you ASAP. > > Have fun :-) > > Rob M. > > > > Tim Burgess wrote: > >> Hi, >> Still tryin' to freeze my wxmpl matplotlib application.... sigh. >> >> This is wxpython + wxmpl + matplotlib. This has turned into one hell >> of a fight - BUT I think I am about to win. You have to keep the faith >> :-} >> >> Name the py2exe issue with freezing matplotlib / wxmpl and I have been >> there fought that. I have slayed many dragons... >> >> I now have a problem that has been asked before on this list. I have >> tried the answer that was offered- it didnt help. I think I am in a >> postion to ask a simple solid question... >> >> When I run my application I see this.... >> >> Fatal Python error: Call to API function without first calling >> import_libnumarray() in Src\_convmodule.c >> >> This application has requested the Runtime to terminate it in an >> unusual way. >> Please contact the application's support team for more information. >> >> I added import numarray all over the place... a previous post >> suggested that maybe Wxpython was calling numarray before I was... no >> I dont think wxpython and numarray ever need each other. >> >> To help prove this I changed my application to this: (a boa app - so >> this code occurs early in execution but not before wxpython has been >> used... >> >> def __init__(self, parent): >> >> import numarray >> import numarray.numarrayall # desperate attempt to stop error >> api call without first calling import_libnumarray >> self._init_ctrls(parent) # init wxpython controls >> >> print numarray.__version__ >> >> and bang my application no longer runs. If I comment out this print >> line, the application runs perfectly except when you click the button >> to draw the graph. Then you get the same error message as above. >> >> BTW in the development environments - application works fine - and >> that's because the development environs are loading the modules from >> the python installation - is my call... >> >> In my library file you can see that numarray is definitely included - >> it's there. >> >> So my question is: >> Q: How do you force the loading (not the inclusion) of the nummary >> module? Or how do you get import_libnumarray to run? >> >> Can some one tell me more about the mechanism python uses to load the >> modules.. What triggers the load call? Where? >> >> I know I am close. Rest of the application is 95% finished. Customer >> loves it. 2 week delay coz I cant freeze the @#$@$%@ thing. >> >> BTW kudos to py2exe developers and maintainers - as I learn more about >> the challenges in identifying the modules and the packaging of them >> etc - I appreciate it. This is not a sucking up effort to get an >> answer - but if it helps.... :-} >> >> thanks >> >> PS I have cross posted this to matploblib and py2exe lists - I am >> desperate! >> > > -- > O__ > _/`.\ > `=( ' > > > ------------------------------------------------------- This SF.Net > email is sponsored by: Power Architecture Resource Center: Free content, > downloads, discussions, and more. > http://solutions.newsforge.com/ibmarch.tmpl |
From: Rob M. <rob...@in...> - 2005-10-19 10:14:11
|
Thanks Werner.. Werner F. Bruhin wrote: > Hi Rob, > > Rob Marino wrote: > >> Suddenly I feel less alone. >> >> .. >> I'm engaged in exactly the same process right now, I've tried moving >> the whole of numarray into the dist a dir out of sheer >> desperation....but no go- my traceback looks like this..... >> >> Traceback (most recent call last): >> Traceback (most recent call last): >> File "HacGui.py", line 21, in ? >> File "activity.pyc", line 17, in ? >> File "matplotlib\axes.pyc", line 5, in ? >> File >> "C:\DOCUME~1\ROBMAR~1\REPO\Hydra2\hydra\admin\client\HAC\build\dist\__init__.pyc", >> line 95, in ? >> >> ImportError: No module named random_array > > If I remember correctly I had solved that by including > "matplotlib.numerix" into the packages to force include in py2exe. > > "packages": ["encodings", "kinterbasdb", "pytz", "matplotlib.numerix"], > > See you > Werner > >> >> As soon as I remove numarray fropm the dist dir this resolves to >> >> >> Fatal Python error: Call to API function without first calling >> import_libnumarray() in Src\_convmodule.c >> >> I came across a post yesterday >> http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/2852995 >> that suggests that it's possible to >> 'force' the whole of numarray into an app. I'd like to know how though >> >> *Russell E. Owen wrote: > If I convert my python code to an >> application (Windows via py2exe or Mac > via bundlebuilder) it fails >> with the following error: > > Fatal Python error: Call to API >> function without first calling > import_libnumarray() in >> Src/_convmodule.c > > This currently (1.3.3) happens when a numarray >> API function is called before the API is successfully initialized. >> Although the message was intended as an aid to extension writers, in >> this case numarray is failing to import altogether. At one point >> numarray had a fatal error for import failures but I removed it at >> someone's request. I've restored it because I think it's most >> commonly fatal anyway and removing the message just obfuscated the >> problem. The non-fatal behavior is now in the _import_libnumarray() >> macro. > I can force *all* of numarray into the application, which >> avoids the > > This is what you need to do. It should be possible to >> factor out (or not explicitly list) numarray's Packages, but core >> numarray is not meant to be distributed in pieces. The many >> type-specific extensions were only added to work around a compiler >> problem, not to lighten binary distributions. ..* >> >> >> >> >> ('.', >> glob.glob(r'C:\PROGRA~1\Python24\share\MATPLO~1\matplotlibrc')), >> ('.', >> glob.glob(r'C:\PROGRA~1\Python24\Lib\SITE-P~1\numarray\*.py')), >> >> ......seems to take care of an earlier error ( can't find >> matplotlibrc file) >> >> You have my complete empathy on this problem. In the event I come up >> with some sort of magic bullet, I'll mail you ASAP. >> >> Have fun :-) >> >> Rob M. >> >> >> >> Tim Burgess wrote: >> >>> Hi, >>> Still tryin' to freeze my wxmpl matplotlib application.... sigh. >>> >>> This is wxpython + wxmpl + matplotlib. This has turned into one hell >>> of a fight - BUT I think I am about to win. You have to keep the >>> faith :-} >>> >>> Name the py2exe issue with freezing matplotlib / wxmpl and I have >>> been there fought that. I have slayed many dragons... >>> >>> I now have a problem that has been asked before on this list. I have >>> tried the answer that was offered- it didnt help. I think I am in a >>> postion to ask a simple solid question... >>> >>> When I run my application I see this.... >>> >>> Fatal Python error: Call to API function without first calling >>> import_libnumarray() in Src\_convmodule.c >>> >>> This application has requested the Runtime to terminate it in an >>> unusual way. >>> Please contact the application's support team for more information. >>> >>> I added import numarray all over the place... a previous post >>> suggested that maybe Wxpython was calling numarray before I was... >>> no I dont think wxpython and numarray ever need each other. >>> >>> To help prove this I changed my application to this: (a boa app - so >>> this code occurs early in execution but not before wxpython has been >>> used... >>> >>> def __init__(self, parent): >>> >>> import numarray >>> import numarray.numarrayall # desperate attempt to stop error >>> api call without first calling import_libnumarray >>> self._init_ctrls(parent) # init wxpython controls >>> >>> print numarray.__version__ >>> >>> and bang my application no longer runs. If I comment out this print >>> line, the application runs perfectly except when you click the >>> button to draw the graph. Then you get the same error message as above. >>> >>> BTW in the development environments - application works fine - and >>> that's because the development environs are loading the modules from >>> the python installation - is my call... >>> >>> In my library file you can see that numarray is definitely included >>> - it's there. >>> >>> So my question is: >>> Q: How do you force the loading (not the inclusion) of the nummary >>> module? Or how do you get import_libnumarray to run? >>> >>> Can some one tell me more about the mechanism python uses to load >>> the modules.. What triggers the load call? Where? >>> >>> I know I am close. Rest of the application is 95% finished. Customer >>> loves it. 2 week delay coz I cant freeze the @#$@$%@ thing. >>> >>> BTW kudos to py2exe developers and maintainers - as I learn more >>> about the challenges in identifying the modules and the packaging of >>> them etc - I appreciate it. This is not a sucking up effort to get >>> an answer - but if it helps.... :-} >>> >>> thanks >>> >>> PS I have cross posted this to matploblib and py2exe lists - I am >>> desperate! >>> >> >> -- >> O__ >> _/`.\ >> `=( ' >> >> >> ------------------------------------------------------- This SF.Net >> email is sponsored by: Power Architecture Resource Center: Free >> content, downloads, discussions, and more. >> http://solutions.newsforge.com/ibmarch.tmpl > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users > > -- O__ _/`.\ `=( ' |
From: Todd M. <jm...@st...> - 2005-10-19 11:09:46
|
Tim Burgess wrote: > Hi, > Still tryin' to freeze my wxmpl matplotlib application.... sigh. > > This is wxpython + wxmpl + matplotlib. This has turned into one hell > of a fight - BUT I think I am about to win. You have to keep the faith > :-} > > Name the py2exe issue with freezing matplotlib / wxmpl and I have been > there fought that. I have slayed many dragons... > > I now have a problem that has been asked before on this list. I have > tried the answer that was offered- it didnt help. I think I am in a > postion to ask a simple solid question... > > When I run my application I see this.... > > Fatal Python error: Call to API function without first calling > import_libnumarray() in Src\_convmodule.c Either an extension in your application forgot to call import_libnumarray() or the numarray distributed as part of your application is incomplete or broken and the import failed. numarray CVS now makes a better report of which is true. > I added import numarray all over the place... a previous post > suggested that maybe Wxpython was calling numarray before I was... no > I dont think wxpython and numarray ever need each other. > > To help prove this I changed my application to this: (a boa app - so > this code occurs early in execution but not before wxpython has been > used... > > def __init__(self, parent): > > import numarray > import numarray.numarrayall # desperate attempt to stop error > api call without first calling import_libnumarray > self._init_ctrls(parent) # init wxpython controls > > print numarray.__version__ > > and bang my application no longer runs. If I comment out this print > line, the application runs perfectly except when you click the button > to draw the graph. Then you get the same error message as above. > > BTW in the development environments - application works fine - and > that's because the development environs are loading the modules from > the python installation - is my call... My guess is that in the development environments numarray is already correctly installed. > > In my library file you can see that numarray is definitely included - > it's there. > > So my question is: > Q: How do you force the loading (not the inclusion) of the nummary module? I may not understand you, but when numarray is all there, "import numarray" should work just like for any other Python package. I think your problem is that numarray is not being included correctly in your installer because it's extension dependencies are hard for py2exe to detect correctly. I believe this is fixed now in numarray CVS. > Or how do you get import_libnumarray to run? import_libnumarray() is something an extension writer must explicitly call in their extension init() if they want to use the numarray API. > Can some one tell me more about the mechanism python uses to load the > modules.. What triggers the load call? Where? > > I know I am close. Rest of the application is 95% finished. Customer > loves it. 2 week delay coz I cant freeze the @#$@$%@ thing. Try using numarray CVS to generate your installer. Last week someone had a similar issue with this and I added code to numarray.__init__ to explicitly import all numarray's core extensions. That user reported that the extra "hints" in numarray.__init__ helped py2exe detect the necessary numarray extension set correctly, numarray was thus installed correctly, and the installer worked. Regards, Todd |
From: John H. <jdh...@ac...> - 2005-10-19 13:15:14
|
>>>>> "Todd" == Todd Miller <jm...@st...> writes: Todd> Either an extension in your application forgot to call Todd> import_libnumarray() or the numarray distributed as part of Todd> your application is incomplete or broken and the import Todd> failed. numarray CVS now makes a better report of which is Todd> true. Could that someone be us? I tried > grep -ri import_libnumarray . in my src tree and got zippo. We call import_array(); .... Is this a matplotlib bug. If so, I'll be happy to patch it and roll out a bug-fix release. JDH |
From: Todd M. <jm...@st...> - 2005-10-19 14:00:29
|
John Hunter wrote: >>>>>>"Todd" == Todd Miller <jm...@st...> writes: >>>>>> >>>>>> > > Todd> Either an extension in your application forgot to call > Todd> import_libnumarray() or the numarray distributed as part of > Todd> your application is incomplete or broken and the import > Todd> failed. numarray CVS now makes a better report of which is > Todd> true. > >Could that someone be us? > > I don't think so. For matplotlib we use import_array() because that's the init call for numarray's Numeric compatible interface. I think Tim's import_libnumarray() message is originating from numarray as it tries to call it's own API, most likely because the numarray installation is broken so the import failed. Here's a couple other facts: 1. The import_libnumarray() message is confusing because I didn't think numarray import failures would occur in a sane world... so import failures in numarray-1.3.3 look the same as uninitialized extensions. 2. numarray uses it's own API to share code internally, so when numarray's rather complex import fails, the first internal call to it's own API generates the cryptic fatal error. numarray CVS does two new things that are about a week old: 1. It correctly reports numarray's own import failure with a fatal error. This should clarify future problems if there are any. 2. Explicit imports of core extensions were added to numarray.__init__ so that py2exe can figure out what extensions must be included in an installer. This should actually solve the problem. Those fixes address "exactly the same symptoms" (py2exe + cryptic fatal unitialized API error message) seen by another user who tested the fix on two different installer tools. >I tried > > > grep -ri import_libnumarray . > >in my src tree and got zippo. > >We call > > import_array(); > >.... > >Is this a matplotlib bug. If so, I'll be happy to patch it and roll >out a bug-fix release. > > Nope, don't think so. Todd |
From: Ken M. <mc...@ii...> - 2005-10-20 16:46:29
|
On Oct 19, 2005, at 3:08 AM, Tim Burgess wrote: > Fatal Python error: Call to API function without first calling > import_libnumarray() in Src\_convmodule.c It looks like someone who was having the same problem got some reasonable advice from the numpy-discussion mailing list: http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/2852995 From the posting, it sounds like you need to figure out how to make py2exe include all of numarray. I would start out by py2exe-ing a short test script that just imports numarray and makes an array, then moving on to your full application after you get that working. > I added import numarray all over the place... a previous post > suggested that maybe Wxpython was calling numarray before I was... no > I dont think wxpython and numarray ever need each other. That's not going to fix the problem: the error is referring to a C macro/function called `import_numarray' that is apparently supposed to be called while numarray is initializing itself. In the email linked to above, Todd Miller says that this is indicative of numarray being incompletely included by py2exe. > In my library file you can see that numarray is definitely included - > it's there. All of it? I think you should should probably check that the numarray package bundled in the py2exe zip file is identical to the one in site-packages (i.e. the number of files is the same). Ken |