[SciPy-Dev] request for testing: SciPy 0.7.2 RC1 + NumPy 1.4.1 RC1

David Cournapeau cournape@gmail....
Tue Apr 6 09:44:34 CDT 2010


On Tue, Apr 6, 2010 at 12:38 PM, Ralf Gommers
<ralf.gommers@googlemail.com> wrote:
>
>
> On Tue, Apr 6, 2010 at 11:08 AM, Alan G Isaac <aisaac@american.edu> wrote:
>>
>> Python 2.6.5 (32bit) on Vista (64bit), no gcc.
>> Alan Isaac
>>
>> c:\Python26\lib\site-packages\scipy\spatial\__init__.py:7: RuntimeWarning:
>> numpy.dtype size changed, may indicate binary incompatibility
>>   from ckdtree import *
>> c:\Python26\lib\site-packages\scipy\spatial\__init__.py:7: RuntimeWarning:
>> numpy.flatiter size changed, may indicate binary incompatibility
>>   from ckdtree import *
>> c:\Python26\lib\site-packages\scipy\linsolve\__init__.py:4:
>> DeprecationWarning: scipy.linsolve has moved to scipy.sparse.linalg.dsolve
>>   warn('scipy.linsolve has moved to scipy.sparse.linalg.dsolve',
>> DeprecationWarning)
>> c:\Python26\lib\site-packages\scipy\stats\distributions.py:27:
>> RuntimeWarning: numpy.dtype size changed, may indicate binary
>> incompatibility
>>   import vonmises_cython
>> c:\Python26\lib\site-packages\scipy\stats\distributions.py:27:
>> RuntimeWarning: numpy.flatiter size changed, may indicate binary
>> incompatibility
>>   import vonmises_cython
>>
>> ..................................................................................................................................................................................................................
>
> Can you please double check that it's not picking up some left-over from
> 1.4.0 on your system? This really should have been fixed.

The warnings are harmless, because we made sure the structures were
compatible (after the datetime removal in 1.4.x). The flatiter struct
was changed to support the neighborhood iterator, and the dtype still
has the metadata pointer (which we could remove, but I don't think
there is any point). We could remove the warning in the C code as a
temporary workaround for 0.7.x, but it would be nice to be able to
filter those warnings out, at least programmatically from python (by
using a special warning class, for example).

cheers,

David


More information about the SciPy-Dev mailing list