[SciPy-dev] system_info.py, blas_opt_info broken ?

Pearu Peterson pearu at scipy.org
Wed Mar 17 07:38:06 EST 2004



On Wed, 17 Mar 2004, Arnd Baecker wrote:

> I just downloaded the CVS version and doing
>   cd scipy_core/scipy_distutils
>   python system_info.py
> gives
> 
> blas_opt_info:
> Traceback (most recent call last):
>   File "system_info.py", line 1263, in ?
>     show_all()
>   File "system_info.py", line 1260, in show_all
>     r = c.get_info()
>   File
> "/tmp/baecker/CompileDir/scipy/scipy_core/scipy_distutils/system_info.py",
> line 283, in get_info
>     self.calc_info()
>   File
> "/tmp/baecker/CompileDir/scipy/scipy_core/scipy_distutils/system_info.py",
> line 934, in calc_info
>     atlas_version = get_atlas_version(**version_info)
>   File
> "/tmp/baecker/CompileDir/scipy/scipy_core/scipy_distutils/system_info.py",
> line 775, in get_atlas_version
>     from core import Extension, setup
>   File "/tmp/baecker/CompileDir/scipy/scipy_core/scipy_distutils/core.py",
> line 5, in ?
>     from scipy_distutils.dist import Distribution
> ImportError: No module named scipy_distutils.dist

At the moment it is not possible to execute

  python system_info.py

until scipy_distutils is installed first. The reason is that system_info 
tries to compile an extension module to determine the version of ATLAS, 
but do to that, it needs scipy_distutils. One option would be to disable
ATLAS version detection if scipy_distutils is not installed, but then 
again the output of `python system_info.py` would not reflect the real 
state of the system. So, install scipy_core first (or put it's location 
to PYTHONPATH) and then run system_info.py.

> The same happens for lapack_opt_info.
> 
> One more: can one safely ignore
> ======================================================================
> FAIL: check_real (scipy_base.type_check.test_type_check.test_imag)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File
> "/opt/python/lib/python2.3/site-packages/scipy_base/tests/test_type_check.py",
> line 31, in check_real
>     assert_array_equal(0,imag(y))
>   File "/opt/python/lib/python2.3/site-packages/scipy_test/testing.py",
> line 641, in assert_array_equal
>     assert len(shape(x))==len(shape(y)) and \
> AssertionError:
> Arrays are not equal (shapes (), (10,) mismatch):
> 
> ?

Yes, you can ignore it. It's solely an issue of testing hooks and will be 
fixed as soon as I get a moment for it.

Pearu




More information about the SciPy-Dev mailing list