Klaus Nökel wrote: > David, > > >> Klaus Noekel wrote: >> >>> I doubt that the DLL was not physically present and rather suspect a >>> dependency on some other DLL that was missing. The INSTALL.TXT >>> unfortunately was not helpful. Can anybody please explain what other >>> dependencies exist? Anything else I need to install? >>> >>> >> This exact problem is specific to IDLE - I don't know what triggers it. >> Today, the best solution for a 64 bits numpy on windows is to built it >> yourself with MS compilers - the distributed one is built with mingw >> compilers, and there still seems to be some stability problems with >> those. Unfortunately, as the mingw debugger does not work either on 64 >> bits archs, finding the problem is quite hard. >> >> > > I don't believe that the problem is specific to IDLE. Python also crashes > when I put nothing but "import numpy" in a file and execute it with > python.exe. > > Regarding the note on building numpy myself: the discussion in this forum > scared me a little, because of the challenge to build LAPACK with a > compatible Fortran compiler etc. That and the fact that I do not have MSVC > 2008 (only 2005) keeps me from trying it. Any chance that a MS-based > installer will materialize soon? Or are there any mingw-specific runtime > libraries that I need to install so that the mingw-based numpy works? > > Thanks for your help! > Klaus Noekel > > > > Hi, I also see this. What version of Python specific of Python are you using? I got the same with Python 2.6.1 so perhaps I need to downgrade to Python 2.6.0?
Bruce _______________________________________________ Numpy-discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
