[Numpy-discussion] ANN: NumPy 1.6.1 release candidate 2

Bruce Southey bsouthey at gmail.com
Thu Jul 7 12:11:51 EDT 2011


On 07/07/2011 10:06 AM, Mark Wiebe wrote:
> On Thu, Jul 7, 2011 at 9:56 AM, Bruce Southey <bsouthey at gmail.com 
> <mailto:bsouthey at gmail.com>> wrote:
>
>     On Wed, Jul 6, 2011 at 1:56 PM, Christoph Gohlke <cgohlke at uci.edu
>     <mailto:cgohlke at uci.edu>> wrote:
>     >
>     >
>     > On 7/6/2011 10:57 AM, Russell E. Owen wrote:
>     >> In article
>     >>
>     <CABL7CQhNnjkzK9XNrLVDArSdKNwRM4eV0mXdUrJSaXq73EbwcQ at mail.gmail.com <mailto:CABL7CQhNnjkzK9XNrLVDArSdKNwRM4eV0mXdUrJSaXq73EbwcQ at mail.gmail.com>>,
>     >>   Ralf Gommers<ralf.gommers at googlemail.com
>     <mailto:ralf.gommers at googlemail.com>>  wrote:
>     >>
>     >>> On Tue, Jul 5, 2011 at 11:41 PM, Russell E. Owen<rowen at uw.edu
>     <mailto:rowen at uw.edu>>  wrote:
>     >>>
>     >>>> In article<BANLkTi=LXiTcrv1LgMtP=p9nF8eMr8=+hw at mail.gmail.com
>     <mailto:hw at mail.gmail.com>>,
>     >>>>   Ralf Gommers<ralf.gommers at googlemail.com
>     <mailto:ralf.gommers at googlemail.com>>  wrote:
>     >>>>
>     >>>>> https://sourceforge.net/projects/numpy/files/NumPy/1.6.1rc2/
>     >>>>
>     >>>> Will there be a Mac binary for 32-bit pythons (one that is
>     compatible
>     >>>> with older versions of MacOS X)? At present I only see a 64-bit
>     >>>> 10.6-only version.
>     >>>>
>     >>>>
>     >>>> Yes there will be for the final release (10.4-10.6
>     compatible). I can't
>     >>> create those on my own computer, so sometimes I don't make
>     them for RCs.
>     >>
>     >> I'm glad they will be present for the final release.
>     >>
>     >> FYI: I built my own 1.6.1rc2 against Python 2.7.2 (the 32-bit Mac
>     >> version from python.org <http://python.org>). I reproduced a
>     memory error that I've been
>     >> trying to narrow down. This is ticket 1896:
>     >> <http://projects.scipy.org/numpy/ticket/1896>
>     >> and the problem is also in 1.6.0.
>     >>
>     >> -- Russell
>     >>
>     >
>     >
>     > I can reproduce this error on Windows. It looks like a serious
>     regression.
>     >
>     > Christoph
>     > _______________________________________________
>     > NumPy-Discussion mailing list
>     > NumPy-Discussion at scipy.org <mailto:NumPy-Discussion at scipy.org>
>     > http://mail.scipy.org/mailman/listinfo/numpy-discussion
>     >
>     I do get this error in the code without tinker on the first loop.
>
>     I did notice that the original array (dataArr) is float64 but the
>     second array (scaledArr) is only float32. The problem is removed by
>     changing the dtype of scaledArr to float64. Thus, it would appear some
>     memory allocation related error to squeeze a float64 result into a
>     memory allocated for a float32 array.
>
>
> Can you try it on your platform with the pull request I've made which 
> hopefully fixes it?  Here's the link:
>
> https://github.com/numpy/numpy/pull/103
>
> Thanks,
> Mark
>
>
I do not get the crash with Python2.7 on the users code. But I can not 
compile this branch under Python3.1 or Python3.2. The last error is 
below - I can look into this more if needed.

Bruce


creating build/temp.linux-x86_64-3.1/numpy/core/src/multiarray
compile options: '-Inumpy/core/include 
-Ibuild/src.linux-x86_64-3.1/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/usr/include/python3.1 
-Ibuild/src.linux-x86_64-3.1/numpy/core/src/multiarray 
-Ibuild/src.linux-x86_64-3.1/numpy/core/src/umath -c'
gcc: numpy/core/src/multiarray/multiarraymodule_onefile.c
In file included from 
numpy/core/src/multiarray/multiarraymodule_onefile.c:17:0:
numpy/core/src/multiarray/arraytypes.c.src: In function ‘VOID_getitem’:
numpy/core/src/multiarray/arraytypes.c.src:631:94: error: 
‘NPY_WRITEABLE’ undeclared (first use in this function)
numpy/core/src/multiarray/arraytypes.c.src:631:94: note: each undeclared 
identifier is reported only once for each function it appears in
numpy/core/src/multiarray/arraytypes.c.src:633:35: warning: assignment 
from incompatible pointer type
In file included from 
numpy/core/src/multiarray/multiarraymodule_onefile.c:28:0:
numpy/core/src/multiarray/getset.c: In function ‘array_data_get’:
numpy/core/src/multiarray/getset.c:284:5: warning: passing argument 1 of 
‘PyMemoryView_FromObject’ from incompatible pointer type
/usr/include/python3.1/memoryobject.h:54:12: note: expected ‘struct 
PyObject *’ but argument is of type ‘struct PyArrayObject *’
numpy/core/src/multiarray/multiarraymodule_onefile.c: At top level:
numpy/core/src/multiarray/scalartypes.c.src:2231:1: warning: 
‘gentype_getsegcount’ defined but not used
numpy/core/src/multiarray/scalartypes.c.src:2249:1: warning: 
‘gentype_getcharbuf’ defined but not used
numpy/core/src/multiarray/mapping.c:75:1: warning: ‘_array_ass_item’ 
defined but not used
numpy/core/src/multiarray/number.c:266:1: warning: ‘array_divide’ 
defined but not used
numpy/core/src/multiarray/number.c:464:1: warning: 
‘array_inplace_divide’ defined but not used
numpy/core/src/multiarray/buffer.c:25:1: warning: ‘array_getsegcount’ 
defined but not used
numpy/core/src/multiarray/buffer.c:58:1: warning: ‘array_getwritebuf’ 
defined but not used
numpy/core/src/multiarray/buffer.c:71:1: warning: ‘array_getcharbuf’ 
defined but not used
In file included from 
numpy/core/src/multiarray/multiarraymodule_onefile.c:17:0:
numpy/core/src/multiarray/arraytypes.c.src: In function âVOID_getitemâ:
numpy/core/src/multiarray/arraytypes.c.src:631:94: error: 
âNPY_WRITEABLEâ undeclared (first use in this function)
numpy/core/src/multiarray/arraytypes.c.src:631:94: note: each undeclared 
identifier is reported only once for each function it appears in
numpy/core/src/multiarray/arraytypes.c.src:633:35: warning: assignment 
from incompatible pointer type
In file included from 
numpy/core/src/multiarray/multiarraymodule_onefile.c:28:0:
numpy/core/src/multiarray/getset.c: In function âarray_data_getâ:
numpy/core/src/multiarray/getset.c:284:5: warning: passing argument 1 of 
âPyMemoryView_FromObjectâ from incompatible pointer type
/usr/include/python3.1/memoryobject.h:54:12: note: expected âstruct 
PyObject *â but argument is of type âstruct PyArrayObject *â
numpy/core/src/multiarray/multiarraymodule_onefile.c: At top level:
numpy/core/src/multiarray/scalartypes.c.src:2231:1: warning: 
âgentype_getsegcountâ defined but not used
numpy/core/src/multiarray/scalartypes.c.src:2249:1: warning: 
âgentype_getcharbufâ defined but not used
numpy/core/src/multiarray/mapping.c:75:1: warning: â_array_ass_itemâ 
defined but not used
numpy/core/src/multiarray/number.c:266:1: warning: âarray_divideâ 
defined but not used
numpy/core/src/multiarray/number.c:464:1: warning: 
âarray_inplace_divideâ defined but not used
numpy/core/src/multiarray/buffer.c:25:1: warning: âarray_getsegcountâ 
defined but not used
numpy/core/src/multiarray/buffer.c:58:1: warning: âarray_getwritebufâ 
defined but not used
numpy/core/src/multiarray/buffer.c:71:1: warning: âarray_getcharbufâ 
defined but not used
error: Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe 
-Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC 
-fwrapv -fPIC -Inumpy/core/include 
-Ibuild/src.linux-x86_64-3.1/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/usr/include/python3.1 
-Ibuild/src.linux-x86_64-3.1/numpy/core/src/multiarray 
-Ibuild/src.linux-x86_64-3.1/numpy/core/src/umath -c 
numpy/core/src/multiarray/multiarraymodule_onefile.c -o 
build/temp.linux-x86_64-3.1/numpy/core/src/multiarray/multiarraymodule_onefile.o" 
failed with exit status 1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20110707/fb5062a1/attachment.html>


More information about the NumPy-Discussion mailing list