[Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

Ralf Gommers ralf.gommers@googlemail....
Fri Mar 4 22:59:21 CST 2011


On Sat, Mar 5, 2011 at 11:11 AM, Charles R Harris
<charlesr.harris@gmail.com> wrote:
> On Fri, Mar 4, 2011 at 7:49 PM, Charles R Harris <charlesr.harris@gmail.com>
> wrote:
>> On Fri, Mar 4, 2011 at 6:41 PM, Charles R Harris
>> <charlesr.harris@gmail.com> wrote:
>>> On Fri, Mar 4, 2011 at 12:54 PM, Christoph Gohlke <cgohlke@uci.edu>
>>> wrote:
>>>> Most packages don't have any apparent problems.
>>>> Scipy-0.9.0-win-amd64-py3.2 and Bottleneck-0.3.0 each have one test
>>>> failure/error (also listed below).
>>>>
>>>> There is a problem with code generated by Cython 0.13: pytables-2.2.1
>>>> and pandas-0.3.0, which were built with Cython 0.13, report several
>>>> failures and do crash during the tests. This can probably be fixed by
>>>> "recythonizing" with Cython 0.14.1.
>>>>
>>>
>>> I see pytables crash on Fedora 14 64 bit also, even with freshly built
>>> pytables/numexpr.

That's actually good news, right? Looks like it's not due to a
backwards incompatibility.

On a related note, can we do something about this:

$ python setup.py build_ext -i
Running from numpy source directory.non-existing path in
'numpy/distutils': 'site.cfg'
F2PY Version 2
numpy/core/setup_common.py:86: MismatchCAPIWarning: API mismatch
detected, the C API version numbers have to be updated. Current C api
version is 5, with checksum 941534d1afbc085b996141e8027d1d1e, but
recorded checksum for C API version 5 in codegen_dir/cversions.txt is
77e2e846db87f25d7cf99f9d812076f0. If functions were added in the C
API, you have to update C_API_VERSION  in numpy/core/setup_common.py.
  MismatchCAPIWarning)


Ralf


>> Backtrace
>>
>> #0  0x0000003e9647a52c in __libc_free (mem=0x16cd1f0) at malloc.c:3724
>> #1  0x00007fffefed0988 in array_dealloc (self=0x29617b0)
>>     at numpy/core/src/multiarray/arrayobject.c:266
>> #2  0x0000003ea84e8452 in PyEval_EvalFrameEx (f=<value optimized out>,
>>     throwflag=<value optimized out>)
>>     at /usr/src/debug/Python-2.7/Python/ceval.c:2344
>> #3  0x0000003ea84ea71d in fast_function (f=<value optimized out>,
>>     throwflag=<value optimized out>)
>>     at /usr/src/debug/Python-2.7/Python/ceval.c:4157
>> #4  call_function (f=<value optimized out>, throwflag=<value optimized
>> out>)
>>     at /usr/src/debug/Python-2.7/Python/ceval.c:4092
>>
>>
>
> And a test failure before the crash:
>
> Running MDAtomReopen.test01a_assign
> -----------------------------------
>
> Error in test::
>
>   ValueError: value parameter '[[[1 3]
>   [4 5]]]' cannot be converted into an array object
> compliant with CArray: '/test (CArray(1,)) ''
>   atom := Int32Atom(shape=(2, 2), dflt=array([[0, 0],
>        [0, 0]], dtype=int32))
>   maindim := 0
>   flavor := 'numpy'
>   byteorder := 'little'
>   chunkshape := (4096,)' The error was: <non-broadcastable output operand
> with shape (2,2) doesn't match the broadcast shape (2,2,1)>
>
> Chuck


More information about the NumPy-Discussion mailing list