[SciPy-user] Test bug with Python 2.5.3 on Mac OS X

Joshua Lippai discerptor@gmail....
Sat Dec 20 03:56:14 CST 2008


Hello all,

I decided to give the new bugfix release of Python 2.5 a whirl, and
even after doing a fresh build and install of both NumPy and SciPy,
scipy.test() runs into a snag and gives me a Bus Error, crashing
Python. I built and installed a framework build using GCC 4.2.1, as I
successfully did with Python 2.5.2 before this. Below is the test's
output:

Running unit tests for scipy
NumPy version 1.3.0.dev6174
NumPy is installed in
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy
SciPy version 0.7.0.dev5280
SciPy is installed in
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/scipy
Python version 2.5.3 (r253:67855, Dec 20 2008, 01:13:31) [GCC 4.2.1
(Apple Inc. build 5566)]
nose version 0.10.4
..............[[   2.    5.  138.    2.]
 [   3.    4.  219.    2.]
 [   0.    7.  255.    3.]
 [   1.    8.  268.    4.]
 [   6.    9.  295.    6.]] [[   2.    5.  138.    2.]
 [   3.    4.  219.    2.]
 [   0.    7.  255.    3.]
 [   1.    8.  268.    4.]
 [   6.    9.  295.    6.]]
..0.0
.3.33333332492e-06
.3.32912455292e-06
.3.32912455292e-06
.1.09653997882e-07
.1.98734938506e-07
.4.46252451203e-06
.1.01277823406e-06
.0.0
.3.33333335334e-06
.3.33333335334e-06
.3.33333335334e-06
............................................(array([53, 55, 56]),
array([2, 3, 1])) (array([53, 55, 56]), array([2, 3, 1])) [2 2 2 2 2 2
2 2 2 2 3 3 3 3 3 3 3 3 3 3 1 1 1 1 1 1 1 1 1 1]
..........7.54931229197e-08
.7.54931229197e-08
...1.09653997882e-07
..7.54931229197e-08
.........(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
...(1, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
...(1, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
...(1, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
...(1, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
.(29, 4)
...(1, 4)
........[[  3   6 138]
 [  4   5 219]
 [  1   8 255]
 [  2   9 268]
 [  7  10 295]] [[   3.    6.  138.]
 [   4.    5.  219.]
 [   1.    8.  255.]
 [   2.    9.  268.]
 [   7.   10.  295.]]
............................................................................../Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/scipy/interpolate/fitpack2.py:498:
UserWarning:
The coefficients of the spline returned have been computed as the
minimal norm least-squares solution of a (numerically) rank deficient
system (deficiency=7). If deficiency is large, the results may be
inaccurate. Deficiency may strongly depend on the value of eps.
  warnings.warn(message)
...../Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/scipy/interpolate/fitpack2.py:439:
UserWarning:
The required storage space exceeds the available storage space: nxest
or nyest too small, or s too small.
The weighted least-squares spline corresponds to the current set of
knots.
  warnings.warn(message)
...........................................K..K.......................................................................................................................................Warning:
1000000 bytes requested, 20 bytes read.
./Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/lib/utils.py:108:
DeprecationWarning: write_array is deprecated
  warnings.warn(str1, DeprecationWarning)
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/lib/utils.py:108:
DeprecationWarning: read_array is deprecated
  warnings.warn(str1, DeprecationWarning)
....................../Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/lib/utils.py:108:
DeprecationWarning: npfile is deprecated
  warnings.warn(str1, DeprecationWarning)
Bus error


Can anyone else reproduce this, or is this some oddity in my install?
I know NumPy now has a failure in testing its arcsinh(-2j) against
cmath's result due to what I assume is a change to cmath in 2.5.3 to
match that in 2.6+, but that doesn't seem to have anything to do with
this problem, which looks like some weird memory issue. Any ideas?
Thanks in advance.

Josh


More information about the SciPy-user mailing list