[Numpy-discussion] Tests fail in SVN r2165
Sasha
ndarray at mac.com
Fri Feb 24 14:43:08 EST 2006
I've located the culprit. Once I revert numpy/core/__init__.py to
2164, tests pass.
The change appears to postpone the import of NumpyTest:
> svn diff -r 2164:2165 numpy/core/__init__.py
Index: numpy/core/__init__.py
===================================================================
--- numpy/core/__init__.py (revision 2164)
+++ numpy/core/__init__.py (revision 2165)
@@ -25,5 +25,6 @@
__all__ += rec.__all__
__all__ += char.__all__
-from numpy.testing import ScipyTest
-test = ScipyTest().test
+def test(level=1, verbosity=1):
+ from numpy.testing import NumpyTest
+ return NumpyTest().test(level, verbosity)
<http://projects.scipy.org/scipy/numpy/changeset/2165#file2>
I don't understand why this causes problems on my system, but it does. Pearu?
On 2/24/06, Sasha <ndarray at mac.com> wrote:
> I've reverted to r2164 and everything is back to normal. This
> suggests that r2165 changes are at fault and not my setup. That
> change deals with imports and the failure that I see happens during
> import.
>
> I've tried NUMPY_IMPORT_DEBUG=1 and got this:
>
> Executing 'import testing' ... ok
> Executing 'from testing import ScipyTest' ... ok
> Executing 'from testing import NumpyTest' ... ok
> Executing 'import core' ... ok
> Executing 'from core import *' ... ok
> Executing 'import random' ... ok
> Executing 'from random import rand' ... ok
> Executing 'from random import randn' ... ok
> Executing 'import lib' ... ok
> Executing 'from lib import *' ... ok
> Executing 'import linalg' ... ok
> Executing 'import dft' ... ok
> Executing 'from dft import fft' ... ok
> Executing 'from dft import ifft' ... ok
> Found 4 tests for numpy.lib.getlimits
> Found 30 tests for numpy.core.numerictypes
> Found 11 tests for numpy.core.umath
> Found 8 tests for numpy.lib.arraysetops
> Found 42 tests for numpy.lib.type_check
> Found 83 tests for numpy.core.multiarray
> Found 3 tests for numpy.dft.helper
> Found 27 tests for numpy.core.ma
> Traceback (most recent call last):
> ...
>
> Any suggestions for further diagnostic?
>
>
> On 2/24/06, Albert Strasheim <fullung at gmail.com> wrote:
> > Works for me. Just built revision 2165 on Windows with Visual Studio.
> >
> > Python 2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC v.1310 32 bit (Intel)]
> >
> > In [1]: import numpy
> >
> > In [2]: numpy.test()
> > Found 83 tests for numpy.core.multiarray
> > Found 3 tests for numpy.lib.getlimits
> > Found 11 tests for numpy.core.umath
> > Found 8 tests for numpy.lib.arraysetops
> > Found 42 tests for numpy.lib.type_check
> > Found 4 tests for numpy.lib.index_tricks
> > Found 30 tests for numpy.core.numerictypes
> > Found 27 tests for numpy.core.ma
> > Found 1 tests for numpy.core.oldnumeric
> > Found 9 tests for numpy.lib.twodim_base
> > Found 8 tests for numpy.core.defmatrix
> > Found 1 tests for numpy.lib.ufunclike
> > Found 33 tests for numpy.lib.function_base
> > Found 3 tests for numpy.dft.helper
> > Found 1 tests for numpy.lib.polynomial
> > Found 6 tests for numpy.core.records
> > Found 14 tests for numpy.core.numeric
> > Found 44 tests for numpy.lib.shape_base
> > Found 0 tests for __main__
> > ............................................................................
> > ........................
> > ............................................................................
> > ........................
> > ............................................................................
> > ........................
> > ............................
> > ----------------------------------------------------------------------
> > Ran 328 tests in 0.781s
> >
> > OK
> > Out[2]: <unittest.TextTestRunner object at 0x00F56190>
> >
> > In [3]: numpy.__version__
> > Out[3]: '0.9.6.2165'
> >
> > Cheers
> >
> > Albert
> >
> >
>
More information about the NumPy-Discussion
mailing list