Re: [Numpy-discussion] building numpy/scipy
Thanks for the suggestion Joseph - the scipy test suite runs, but it produces lots of errors. Some deprecation warnings in numpy\lib\utils.py (line 110) and scipy\linalg\decomp.py (line 1173) Than it complains about a '_bad_path_' (doesn't exist or not writable). Couldn't remove <user>\appdata]local\temp\tmpc192_pcat_test (directory not empty) Then the crap hits the fan... the following crashes are all due to: test_polyint.CheckKrogh test_derivative crashes on line 38 of scipy\interpolate\tests\test_polyint.py test_derivatives crashes on line 26 test_empty crashes in the same file on line 73 test_hermite crashes in the same file on line 57 test_high_derivative crashes in the same file on line 44 test_lagrange crashes in the same file on line 19 test_low_derivatives crashes in the same file line 32 test_scalar on line 22 test_shapes_1d_vectorvalue on line 95 test_shapes_scalarvalue on line 76 test_shapes_scalarvalue_derivative on line 82 test_shapes_vectorvalue on line 89 test_shapes_vectorvalue_derivative on line 101 test_vector on line 63 test_wrapper on line 108 The following crashes are due to test_polyint.CheckPiecewise test_construction on line 186 test_derivative on line 193 test_derivatives on line 196 test_incremental on line 217 test_scalar on line 189 test_shapes_scalarvalue on line 221 test_shapes_scalarvalue_derivative on line 227 test_shapes_vectorvalue on line 235 test_shapes_vectorvalue_1d on line 242 test_shapes_vectorvalue_derivative on line 248 test_vector on line 205 test_wrapper on line 255 The following crashes are due to test_polyint.CheckTaylor test_exponential on line 116 Failure: AttributeError ('module' object has no attribute 'byteordercodes') nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name numpyio) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name fblas) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name flapack) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name fblas) AGAIN nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name flapack) AGAIN nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: NameError (name 'pilutil is not defined) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name cobyla) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name nonlin) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name zeros) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: NameError (name 'pilutil is not defined) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: ImportError (cannot import name linsolve) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: AttributeError ('module' object has no attribute '_cephes') nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: NameError (name 'pilutil is not defined) nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName Failure: AttributeError ('module' object has no attribute 'convolve') nose-0.10.30py2.5.egg\nose\loader.py on line 364 in loadTestsFromName That was with nose-0.10.3-py2.5. I upgrades to the latest nose-0.10.4-py2.5, but it still produced an armload of (what look like the same) errors. Does this symptomology point to anything (configuration error, package out of date, ???) At 10:50 AM 1/3/2009, you wrote:
I do not have cygwin in my windows path, so I guess that's already hidden.
I patched d:\programs\python25\lib\distutils\cygwinccompiler.py, line 424 to read
ld_version = StrictVersion(result.group(1).rsplit('.',1)[0])
but I still got crash and a traceback.
David Cournapeau suggested using the scipy superpack, so i tried scipy-0.7.0b1-win32-superpack-python2.5.exe. If there were errors I wouldn't know about them, but running
'python -c 'import scipy; print scipy.__version__ '
produces a version number (0.7.0.dev5180 ... not exactly the 0.7.0b1 you'd expect, but not a stack trace either).
Now all I have to do is find some test cases so I can verify a
On Sat, Jan 3, 2009 at 10:13 AM, Mike Landis
wrote: little deeper than the version number.
If you have nose installed, you can run the scipy test suite with
import scipy scipy.test()
Josef _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
Make sure that when you import scipy that you get the correct version.
import scipy scipy.__file__ 'C:\\Programs\\Python25\\lib\\site-packages\\scipy\\__init__.pyc'
From your error messages, I would think python is loading the source distribution and not the compiled and installed version. It would be helpful to see your actual error messages from nose, with copy and paste, at least the first few and last parts of the nose tests. Your summary error message is not very helpful because it doesn't show your actual error path and trace backs.
When I installed the 0.7.0 b1 superpack on WindowsXP, it worked out of the box. The only thing to do, before installing a new version of numpy or scipy, is to uninstall or delete any old version in site-packages, since the directory names of scipy and numpy do not include version numbers. Installing on top of an old version, can leave some old files around which sometimes cause errors. Josef
participants (2)
-
josef.pktd@gmail.com
-
Mike Landis