[Numpy-discussion] ANN: 1.8.0b2 release.

[Frédéric Bastien]

Hi,

I checkout the dev version of numpy and it fail to compile with this error:

creating
build/temp.linux-x86_64-2.7/build/src.linux-x86_64-2.7/numpy/core/src/multiarray

compile options: '-DHAVE_NPY_CONFIG_H=1 -Inumpy/core/include
-Ibuild/src.linux-x86_64-2.7/numpy/core/include/numpy
-Inumpy/core/src/private -Inumpy/core/src -Inumpy/core
-Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath
-Inumpy/core/src/npysort -Inumpy/core/include
-I/opt/lisa/os/epd-7.1.2/include/python2.7 -c'

gcc: numpy/core/src/multiarray/sequence.c

gcc: numpy/core/src/multiarray/descriptor.c

gcc: numpy/core/src/multiarray/getset.c

gcc: numpy/core/src/multiarray/arrayobject.c

gcc: numpy/core/src/multiarray/methods.c

numpy/core/src/multiarray/methods.c: In function ‘array_partition’:

numpy/core/src/multiarray/methods.c:1199:38: error:
‘PyArray_SelectkindConverter’ undeclared (first use in this function)

numpy/core/src/multiarray/methods.c:1199:38: note: each undeclared
identifier is reported only once for each function it appears in

numpy/core/src/multiarray/methods.c: In function ‘array_argpartition’:

numpy/core/src/multiarray/methods.c:1316:38: error:
‘PyArray_SelectkindConverter’ undeclared (first use in this function)

numpy/core/src/multiarray/methods.c:1352:9: warning: assignment makes
pointer from integer without a cast

numpy/core/src/multiarray/methods.c: In function ‘array_partition’:

numpy/core/src/multiarray/methods.c:1199:38: error:
‘PyArray_SelectkindConverter’ undeclared (first use in this function)

numpy/core/src/multiarray/methods.c:1199:38: note: each undeclared
identifier is reported only once for each function it appears in

numpy/core/src/multiarray/methods.c: In function ‘array_argpartition’:

numpy/core/src/multiarray/methods.c:1316:38: error:
‘PyArray_SelectkindConverter’ undeclared (first use in this function)

numpy/core/src/multiarray/methods.c:1352:9: warning: assignment makes
pointer from integer without a cast

error: Command "gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -O2 -fPIC
-DHAVE_NPY_CONFIG_H=1 -Inumpy/core/include
-Ibuild/src.linux-x86_64-2.7/numpy/core/include/numpy
-Inumpy/core/src/private -Inumpy/core/src -Inumpy/core
-Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath
-Inumpy/core/src/npysort -Inumpy/core/include
-I/opt/lisa/os/epd-7.1.2/include/python2.7 -c
numpy/core/src/multiarray/methods.c -o
build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/methods.o" failed
with exit status 1


PyArray_SelectkindConverter is defined in
numpy/core/src/multiarray/conversion_utils.c. methods.c include
conversion_utils.h, but there is no fct declaration of this fct in this
file. Is that normal?

Fred


On Sun, Sep 8, 2013 at 8:55 PM, Charles R Harris
<charlesr.harris at gmail.com>wrote:

>
>
>
> On Sun, Sep 8, 2013 at 6:36 PM, Charles R Harris <
> charlesr.harris at gmail.com> wrote:
>
>>
>>
>>
>> On Sun, Sep 8, 2013 at 3:45 PM, Christoph Gohlke <cgohlke at uci.edu> wrote:
>>
>>> On 9/8/2013 12:14 PM, Charles R Harris wrote:
>>> > Hi all,
>>> >
>>> > I'm happy to announce the second beta release of Numpy 1.8.0. This
>>> > release should solve the Windows problems encountered in the first
>>> beta.
>>> > Many thanks to Christolph Gohlke and Julian Taylor for their hard work
>>> > in getting those issues settled.
>>> >
>>> > It would be good if folks running OS X could try out this release and
>>> > report any issues on the numpy-dev mailing list. Unfortunately the
>>> files
>>> > still need to be installed from source as dmg files are not avalable at
>>> > this time.
>>> >
>>> > Source tarballs and release notes can be found at
>>> > https://sourceforge.net/projects/numpy/files/NumPy/1.8.0b2/. The
>>> Windows
>>> > and OS X installers will follow when the infrastructure issues are
>>> dealt
>>> > with.
>>> >
>>> > Chuck
>>> >
>>>
>>>
>>> Hello,
>>>
>>> I tested numpy 1.8.0b2 with Visual Studio and Intel MKL on Python 2.7
>>> and 3.3 for Windows, 32 and 64 bit. There's only a single test failure
>>> on win-amd64-py3.3, which looks strange since the test expects a
>>> TypeError to be raised.
>>>
>>> ======================================================================
>>> ERROR: test_record_no_hash (test_multiarray.TestRecord)
>>> ----------------------------------------------------------------------
>>> Traceback (most recent call last):
>>>    File
>>> "X:\Python33\lib\site-packages\numpy\core\tests\test_multiarray.py",
>>> line 2464, in test_record_no_hash
>>>      self.assertRaises(TypeError, hash, a[0])
>>>    File "X:\Python33\lib\unittest\case.py", line 570, in assertRaises
>>>      return context.handle('assertRaises', callableObj, args, kwargs)
>>>    File "X:\Python33\lib\unittest\case.py", line 135, in handle
>>>      callable_obj(*args, **kwargs)
>>>    File "X:\Python33\lib\unittest\case.py", line 153, in __exit__
>>>      self.obj_name))
>>> TypeError: unhashable type: 'writeable void-scalar'
>>>
>>>
>>>
>> Hmm, that *is* strange.
>>
>> I don't know what to make of the scipy errors at first glance.
>>
>> <snip>
>>
>>
> I'm going to guess self.assertRaises tried to hash it again, raising the
> error again, and we see the second one. The assertRaises from numpy.testing
> might not have that problem.
>
> Chuck
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20130909/00d00650/attachment.html>