On Tue, Dec 14, 2010 at 5:43 AM, Pauli Virtanen
<pav@iki.fi> wrote:
On Mon, 13 Dec 2010 10:18:13 -0800, Christoph Gohlke wrote:
[clip]
> I ran into the following issues with scipy 0.9.0b1 on Windows when
> building with msvc 9 and intel 11.1 compilers. Numpy is version 1.5.1,
> linked against MKL.
>
> 1) after patching some source files and setup scripts (see msvc9.diff
> attachment), "python setup.py bdist_winist" succeeds on 32- and 64-bit
> Python 2.6, 2.7, and 3.1. The Visual C compiler reproducibly crashes
> while compiling scipy\special\cephes\ndtr.c. Running the build command
> again (without cleaning the build directory) seems to work.
Some of that patch should end up in the tree? I'm not sure which parts,
though.
[clip]
> 2) the build process fails on Python 3.2b1 with the following errors:
>
> scipy\sparse\sparsetools\csr_wrap.cxx(2451) : error C3861:
> 'PyCObject_Import': identifier not found
> scipy\sparse\sparsetools\csr_wrap.cxx(2521) : error C3861:
> 'PyCObject_FromVoidPtr': identifier not found
> scipy\sparse\sparsetools\csr_wrap.cxx(2544) : error C3861:
> 'PyCObject_AsVoidPtr': identifier not found
It seems that the version of SWIG used there is not compatible with
Python 3.2.
[clip]
> FAIL: Real-valued Bessel domains
[clip]
> AssertionError: (nan, nan, nan, nan)
This indicates some issue with AMOS and ifort. What do you get from
import warnings, scipy.special as sc
warnings.simplefilter('always', sc.SpecialFunctionWarning)
sc.errprint(1)
sc.airye(-1)
It's possible that the test is too strict.
This smells like something triggering a DeprecationWarning when GIL is
released. If so, it should be compiler independent and reproducible on
wine+mingw. Or, some PyCObject/PyCapsule issue.
On wine+mingw there are no crashes. With 3.1 there are no DeprecationWarning's, with 2.7 there is one:
Z:\Users\rgommers\.wine\drive_c\Python27\lib\site-packages\scipy\ndimage\morphology.py:254: PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7. Please use capsule objects instead.
structure, mask, output, border_value, origin, invert, cit, 1)
Other than that there is one other (unrelated) failure that I don't think has been reported before, see below. Full test logs are attached.
Cheers,
Ralf
======================================================================
FAIL: test_linesearch.TestLineSearch.test_line_search_wolfe1
----------------------------------------------------------------------
Traceback (most recent call last):
File "Z:\Users\rgommers\.wine\drive_c\Python27\lib\site-packages\nose-0.11.4-py2.7.egg\nose\case.py", line 186, in runTest
self.test(*self.arg)
File "Z:\Users\rgommers\.wine\drive_c\Python27\lib\site-packages\scipy\optimize\tests\test_linesearch.py", line 165, in test_line_search_wolfe1
assert_equal(gv, fprime(x + s*p))
File "Z:\Users\rgommers\.wine\drive_c\Python27\lib\site-packages\numpy\testing\utils.py", line 256, in assert_equal
return assert_array_equal(actual, desired, err_msg, verbose)
File "Z:\Users\rgommers\.wine\drive_c\Python27\lib\site-packages\numpy\testing\utils.py", line 686, in assert_array_equal
verbose=verbose, header='Arrays are not equal')
File "Z:\Users\rgommers\.wine\drive_c\Python27\lib\site-packages\numpy\testing\utils.py", line 618, in assert_array_compare
raise AssertionError(msg)
AssertionError:
Arrays are not equal
(mismatch 35.0%)
x: array([ 0.59815369, 16.47021747, 3.04622715, 15.93277506,
10.10616782, -10.90475125, -10.885384 , 1.20593902,
9.66558674, -8.59479687, 2.08976118, 15.85496522,...
y: array([ 0.59815369, 16.47021747, 3.04622715, 15.93277506,
10.10616782, -10.90475125, -10.885384 , 1.20593902,
9.66558674, -8.59479687, 2.08976118, 15.85496522,...