Hello,
I checked-out the latest trunk and make a new installation of NumPy. My
question: Is it a known behaviour that this action will result with
re-building other packages that are dependent on NumPy. In my case, I had to
re-built matplotlib, and now scipy.
Here is the error message that I am getting while I try to import a scipy
module:
I[1]: run lab4.py
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call last)
RuntimeError: FATAL: module compiled aslittle endian, but detected different
endianness at runtime
---------------------------------------------------------------------------
ImportError Traceback (most recent call last)
/home/gsever/AtSc450/labs/04_thermals/lab4.py in <module>()
2
3 import numpy as np
----> 4 from scipy import stats
5
6
/home/gsever/Desktop/python-repo/scipy/scipy/stats/__init__.py in <module>()
5 from info import __doc__
6
----> 7 from stats import *
8 from distributions import *
9 from rv import *
/home/gsever/Desktop/python-repo/scipy/scipy/stats/stats.py in <module>()
196 # Scipy imports.
197 from numpy import array, asarray, dot, ma, zeros, sum
--> 198 import scipy.special as special
199 import scipy.linalg as linalg
200 import numpy as np
/home/gsever/Desktop/python-repo/scipy/scipy/special/__init__.py in
<module>()
6 #from special_version import special_version as __version__
7
----> 8 from basic import *
9 import specfun
10 import orthogonal
/home/gsever/Desktop/python-repo/scipy/scipy/special/basic.py in <module>()
6
7 from numpy import *
----> 8 from _cephes import *
9 import types
10 import specfun
ImportError: numpy.core.multiarray failed to import
WARNING: Failure executing file:
On Wed, Oct 7, 2009 at 09:55, Gökhan Sever
Hello,
I checked-out the latest trunk and make a new installation of NumPy. My question: Is it a known behaviour that this action will result with re-building other packages that are dependent on NumPy. In my case, I had to re-built matplotlib, and now scipy.
Known issue. See the thread "Numpy SVN broken". -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
I have seen that message, but I wasn't sure these errors were directly
connected since he mentions of getting segfaults whereas in my case only
gives import errors. Building a new copy of scipy fixed this error.
On Wed, Oct 7, 2009 at 10:10 AM, Robert Kern
On Wed, Oct 7, 2009 at 09:55, Gökhan Sever
wrote: Hello,
I checked-out the latest trunk and make a new installation of NumPy. My question: Is it a known behaviour that this action will result with re-building other packages that are dependent on NumPy. In my case, I had to re-built matplotlib, and now scipy.
Known issue. See the thread "Numpy SVN broken".
-- Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
-- Gökhan
You can pull the patches from David's fix_abi branch:
http://github.com/cournape/numpy/tree/fix_abi
This branch has been hacked to be ABI compatible with previous versions.
Cheers
Stéfan
2009/10/7 Gökhan Sever
I have seen that message, but I wasn't sure these errors were directly connected since he mentions of getting segfaults whereas in my case only gives import errors. Building a new copy of scipy fixed this error.
participants (3)
-
Gökhan Sever
-
Robert Kern
-
Stéfan van der Walt