Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On 9/13/2013 7:10 PM, Charles R Harris wrote:
Hi Christolph,
Could you debug this a bit?
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'
I don't understand that at all.
snip
Chuck
I could reproduce the weirdness outside the testsuite on 64 bit Python
3.2, 3.3 and 3.4. It looks like the interpreter gets corrupted.
It could be due to numpy 1.8 using a wrong signature for the hash
function [1] on win-amd64-py3.x. Since Python 3.2 the return value must
be of type `Py_hash_t` (defined as `Py_ssize_t`) [2], not `C long` as
for Python = 3.1.
[1]
https://github.com/numpy/numpy/blob/master/numpy/core/src/multiarray/scalartypes.c.src#L3038
[2] http://docs.python.org/3.2/c-api/typeobj.html#PyTypeObject.tp_hash
Christoph
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
Am 08.09.13 16:14, schrieb Charles R Harris:
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.
Build works (built with latest Anaconda python) but the tests fail on my
machine (OSX 10.8.4):
FAIL: test_mode_raw (test_linalg.TestQR)
--
Traceback (most recent call last):
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/linalg/tests/test_linalg.py,
line 798, in test_mode_raw
old_assert_almost_equal(h, h1, decimal=8)
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/testing/utils.py,
line 454, in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/testing/utils.py,
line 811, in assert_array_almost_equal
header=('Arrays are not almost equal to %d decimals' % decimal))
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/testing/utils.py,
line 644, in assert_array_compare
raise AssertionError(msg)
AssertionError:
Arrays are not almost equal to 8 decimals
(mismatch 83.33%)
x: array([[ 5.91607978, -0.61024233, -1.01707056],
[ 7.43735744, 0.82807867, -3.21391305]])
y: array([[-5.91607978, 0.43377175, 0.72295291],
[-7.43735744, 0.82807867, 0.89262383]])
==
FAIL: test_linalg.test_xerbla
--
Traceback (most recent call last):
File /Users/ck/anaconda/lib/python2.7/site-packages/nose/case.py,
line 197, in runTest
self.test(*self.arg)
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/testing/decorators.py,
line 146, in skipper_func
return f(*args, **kwargs)
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/linalg/tests/test_linalg.py,
line 925, in test_xerbla
assert_(False)
File
/Users/ck/anaconda/lib/python2.7/site-packages/numpy/testing/utils.py,
line 44, in assert_
raise AssertionError(msg)
AssertionError
--
Ran 5235 tests in 264.167s
In [7]: np.__config__.show()
atlas_threads_info:
NOT AVAILABLE
blas_opt_info:
extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']
extra_compile_args = ['-msse3',
'-I/System/Library/Frameworks/vecLib.framework/Headers']
define_macros = [('NO_ATLAS_INFO', 3)]
atlas_blas_threads_info:
NOT AVAILABLE
openblas_info:
NOT AVAILABLE
lapack_opt_info:
extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']
extra_compile_args = ['-msse3']
define_macros = [('NO_ATLAS_INFO', 3)]
atlas_info:
NOT AVAILABLE
lapack_mkl_info:
NOT AVAILABLE
blas_mkl_info:
NOT AVAILABLE
atlas_blas_info:
NOT AVAILABLE
mkl_info:
NOT AVAILABLE
compilers:
GNU Fortran (GCC) 4.2.3
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build
5658) (LLVM build 2336.11.00)
Should I use another compiler?
Regards, Christian
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
14.09.2013 15:15, Christian K. kirjoitti: [clip] FAIL: test_mode_raw (test_linalg.TestQR) FAIL: test_linalg.test_xerbla [clip] Should I use another compiler? Thanks. Both of the above are known issues on OSX, with known fixes (I think fixed in master branch, not sure if backported to 1.8.x). -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Sat, Sep 14, 2013 at 12:12 AM, Christoph Gohlke cgoh...@uci.edu wrote:
On 9/13/2013 7:10 PM, Charles R Harris wrote:
Hi Christolph,
Could you debug this a bit?
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'
I don't understand that at all.
snip
Chuck
I could reproduce the weirdness outside the testsuite on 64 bit Python
3.2, 3.3 and 3.4. It looks like the interpreter gets corrupted.
It could be due to numpy 1.8 using a wrong signature for the hash
function [1] on win-amd64-py3.x. Since Python 3.2 the return value must
be of type `Py_hash_t` (defined as `Py_ssize_t`) [2], not `C long` as
for Python = 3.1.
[1]
https://github.com/numpy/numpy/blob/master/numpy/core/src/multiarray/scalartypes.c.src#L3038
[2] http://docs.python.org/3.2/c-api/typeobj.html#PyTypeObject.tp_hash
That would do it. I'll bet you are right.
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
Hi Christolph,
Could you debug this a bit?
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'
I don't understand that at all.
snip
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
Hi, I create an Ubuntu VM, cloned numpy and it compiled correctly in it. I tried in my normal development environment (instead of a virtualenv) with my old clone that is updated of numpy and it failed. So this isn't virtualenv. I created a new clone of numpy and it compiled correctly with my normal development environment. So this seam to indicate that the __multiarray_api.* are cached. In the new clone, I have this after compilation: $find . -name '*multiarray_api*' ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/multiarray_api.txt ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.h In my old clone, I have this: $cd ../numpy [bastienf@oolong numpy]$find . -name '*multiarray_api*' ./numpy/core/include/numpy/__multiarray_api.h ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/multiarray_api.txt ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.h So for some reason, the __multiarray_api.h file ended in the source of numpy. When this happen all following compilation reuse it instead of regenerating it. If in the new numpy clone, I run: python setup.py build_ext --inplace I get: $find . -name '*multiarray_api*' ./numpy/core/include/numpy/__multiarray_api.c ./numpy/core/include/numpy/multiarray_api.txt ./numpy/core/include/numpy/__multiarray_api.h ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/multiarray_api.txt ./build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.h So this could explain how I ended up with a numpy clone in such state. I think we should make numpy always regenerate the auto-generated files even if they are present, or it would need to check if they are older the the source of thoses files. Do you think this is the good solution too? Do someone have guidance on where those file are generated? Do you and how do you support the partial rebuild vs the full rebuild? Or is it just not supported to build inplace? In the .gitignore file, there is 41 files that seam to be generated. thanks Frédéric On Mon, Sep 9, 2013 at 2:14 PM, Charles R Harris charlesr.har...@gmail.comwrote: On Mon, Sep 9, 2013 at 12:04 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 11:09 AM, Frédéric Bastien no...@nouiz.orgwrote: I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled methods.c. The include aren't part of the env variable, but in the file. Anyway, I think your PR is the good fix. I checked our PR and now I have this new error: gcc: numpy/core/src/multiarray/multiarraymodule.c In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) 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/multiarraymodule.c -o build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/multiarraymodule.o failed with exit status 1 So it seam we have the same problem with those 2 functions. They are defined in numpy/core/src/multiarray/item_selection.c, but not in the .h file. I'm going to guess that there is something special about your virtualenv. snip The prototypes should be in `arrayobject.h` and `ndarrayobject.h`. Perhaps old versions are being used and cached somewhere. Are they precompiled somewhere? Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
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 Fedora 19 linux x86_64 mkl Package ID: l_mkl_11.0.3.163 MKL ERROR: Parameter 4 was incorrect on entry to DGETRF. ... FAIL: test_linalg.test_xerbla -- Traceback (most recent call last): File /usr/lib/python2.7/site-packages/nose/case.py, line 197, in runTest self.test(*self.arg) File /home/nbecker/.local/lib/python2.7/site- packages/numpy/testing/decorators.py, line 146, in skipper_func return f(*args, **kwargs) File /home/nbecker/.local/lib/python2.7/site- packages/numpy/linalg/tests/test_linalg.py, line 925, in test_xerbla assert_(False) File /home/nbecker/.local/lib/python2.7/site- packages/numpy/testing/utils.py, line 44, in assert_ raise AssertionError(msg) AssertionError -- Ran 5271 tests in 56.843s FAILED (KNOWNFAIL=5, SKIP=13, failures=1) nose.result.TextTestResult run=5271 errors=0 failures=1 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
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.har...@gmail.comwrote:
On Sun, Sep 8, 2013 at 6:36 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sun, Sep 8, 2013 at 3:45 PM, Christoph Gohlke cgoh...@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
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.org wrote: 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? No, it looks like a bug. What is strange is that it doesn't show up on my machine. What compiler flags are you using? Could you make a PR for this? snip Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Mon, Sep 9, 2013 at 8:51 AM, Charles R Harris charlesr.har...@gmail.comwrote: On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.org wrote: 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? No, it looks like a bug. What is strange is that it doesn't show up on my machine. What compiler flags are you using? Could you make a PR for this? snip Wait a minute, it is in the API. Try a clean build and see what happens. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Mon, Sep 9, 2013 at 9:33 AM, Frédéric Bastien no...@nouiz.org wrote: I tried it and retried and it still fail. This is in an virtualenv $git show commit c9b06111227f7a4ec213571f97e1b8d19b9c23f5 Merge: 73fbfb2 8edccea Author: Charles Harris charlesr.har...@gmail.com Date: Sun Sep 8 19:47:21 2013 -0700 Merge pull request #3701 from cgohlke/patch-2 ENH: add support for Python 3.4 ast.NameConstant $rm -rf build ## Fail as there is no such directory $pip install . # fail with the same error $pip uninstall numpy $python setup.py install --user # fail with the same error $pip install . ## fail with the same error: $git grep PyArray_SelectkindConverter doc/release/1.8.0-notes.rst:* PyArray_SelectkindConverter numpy/core/code_generators/numpy_api.py: 'PyArray_SelectkindConverter': 298, numpy/core/src/multiarray/conversion_utils.c:PyArray_SelectkindConverter(PyObject *obj, NPY_SELECTKIND *selectkind) numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, Here I don't see PyArray_SelectkindConverter in conversion_utils.h as you said it is present. Witch commit do you use? It's not there, it is part of the API. I've got a PR to add it to the *.h file. The question is why you are the only person (so far) to have a problem compiling. What are your CFLAGS? Chuck Fred On Mon, Sep 9, 2013 at 11:02 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 8:51 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.orgwrote: 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? No, it looks like a bug. What is strange is that it doesn't show up on my machine. What compiler flags are you using? Could you make a PR for this? snip Wait a minute, it is in the API. Try a clean build and see what happens. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled methods.c. The include aren't part of the env variable, but in the file. Anyway, I think your PR is the good fix. I checked our PR and now I have this new error: gcc: numpy/core/src/multiarray/multiarraymodule.c In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) 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/multiarraymodule.c -o build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/multiarraymodule.o failed with exit status 1 So it seam we have the same problem with those 2 functions. They are defined in numpy/core/src/multiarray/item_selection.c, but not in the .h file. thanks Fred On Mon, Sep 9, 2013 at 11:44 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 9:33 AM, Frédéric Bastien no...@nouiz.org wrote: I tried it and retried and it still fail. This is in an virtualenv $git show commit c9b06111227f7a4ec213571f97e1b8d19b9c23f5 Merge: 73fbfb2 8edccea Author: Charles Harris charlesr.har...@gmail.com Date: Sun Sep 8 19:47:21 2013 -0700 Merge pull request #3701 from cgohlke/patch-2 ENH: add support for Python 3.4 ast.NameConstant $rm -rf build ## Fail as there is no such directory $pip install . # fail with the same error $pip uninstall numpy $python setup.py install --user # fail with the same error $pip install . ## fail with the same error: $git grep PyArray_SelectkindConverter doc/release/1.8.0-notes.rst:* PyArray_SelectkindConverter numpy/core/code_generators/numpy_api.py: 'PyArray_SelectkindConverter': 298, numpy/core/src/multiarray/conversion_utils.c:PyArray_SelectkindConverter(PyObject *obj, NPY_SELECTKIND *selectkind) numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, Here I don't see PyArray_SelectkindConverter in conversion_utils.h as you said it is present. Witch commit do you use? It's not there, it is part of the API. I've got a PR to add it to the *.h file. The question is why you are the only person (so far) to have a problem compiling. What are your CFLAGS? Chuck Fred On Mon, Sep 9, 2013 at 11:02 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 8:51 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.orgwrote: 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
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Mon, Sep 9, 2013 at 11:09 AM, Frédéric Bastien no...@nouiz.org wrote: I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled methods.c. The include aren't part of the env variable, but in the file. Anyway, I think your PR is the good fix. I checked our PR and now I have this new error: gcc: numpy/core/src/multiarray/multiarraymodule.c In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) 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/multiarraymodule.c -o build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/multiarraymodule.o failed with exit status 1 So it seam we have the same problem with those 2 functions. They are defined in numpy/core/src/multiarray/item_selection.c, but not in the .h file. I'm going to guess that there is something special about your virtualenv. snip Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Mon, Sep 9, 2013 at 6:09 PM, Frédéric Bastien no...@nouiz.org wrote: I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled methods.c. The include aren't part of the env variable, but in the file. Anyway, I think your PR is the good fix. I checked our PR and now I have this new error: gcc: numpy/core/src/multiarray/multiarraymodule.c In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) 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/multiarraymodule.c -o build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/multiarraymodule.o failed with exit status 1 So it seam we have the same problem with those 2 functions. They are defined in numpy/core/src/multiarray/item_selection.c, but not in the .h file. Something is going horribly wrong with your build process. The API generation code should automatically be putting prototypes for these functions into __multiarray_api.h. I don't understand how you could have a reference to these functions in your __multiarray_api.c without having them in your __multiarray_api.h, though... -n ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Mon, Sep 9, 2013 at 12:04 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 11:09 AM, Frédéric Bastien no...@nouiz.org wrote: I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled methods.c. The include aren't part of the env variable, but in the file. Anyway, I think your PR is the good fix. I checked our PR and now I have this new error: gcc: numpy/core/src/multiarray/multiarraymodule.c In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) 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/multiarraymodule.c -o build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/multiarraymodule.o failed with exit status 1 So it seam we have the same problem with those 2 functions. They are defined in numpy/core/src/multiarray/item_selection.c, but not in the .h file. I'm going to guess that there is something special about your virtualenv. snip The prototypes should be in `arrayobject.h` and `ndarrayobject.h`. Perhaps old versions are being used and cached somewhere. Are they precompiled somewhere? Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
try rebuilding everything from scratch. setup.py dependency handling is a bit dodgy with the generated files. On 09.09.2013 19:09, Frédéric Bastien wrote: I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled methods.c. The include aren't part of the env variable, but in the file. Anyway, I think your PR is the good fix. I checked our PR and now I have this new error: gcc: numpy/core/src/multiarray/multiarraymodule.c In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) In file included from numpy/core/src/multiarray/multiarraymodule.c:3753:0: build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:303:18: error: ‘PyArray_Partition’ undeclared here (not in a function) build/src.linux-x86_64-2.7/numpy/core/include/numpy/__multiarray_api.c:304:18: error: ‘PyArray_ArgPartition’ undeclared here (not in a function) 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/multiarraymodule.c -o build/temp.linux-x86_64-2.7/numpy/core/src/multiarray/multiarraymodule.o failed with exit status 1 So it seam we have the same problem with those 2 functions. They are defined in numpy/core/src/multiarray/item_selection.c, but not in the .h file. thanks Fred On Mon, Sep 9, 2013 at 11:44 AM, Charles R Harris charlesr.har...@gmail.com mailto:charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 9:33 AM, Frédéric Bastien no...@nouiz.org mailto:no...@nouiz.org wrote: I tried it and retried and it still fail. This is in an virtualenv $git show commit c9b06111227f7a4ec213571f97e1b8d19b9c23f5 Merge: 73fbfb2 8edccea Author: Charles Harris charlesr.har...@gmail.com mailto:charlesr.har...@gmail.com Date: Sun Sep 8 19:47:21 2013 -0700 Merge pull request #3701 from cgohlke/patch-2 ENH: add support for Python 3.4 ast.NameConstant $rm -rf build ## Fail as there is no such directory $pip install . # fail with the same error $pip uninstall numpy $python setup.py install --user # fail with the same error $pip install . ## fail with the same error: $git grep PyArray_SelectkindConverter doc/release/1.8.0-notes.rst:* PyArray_SelectkindConverter numpy/core/code_generators/numpy_api.py: 'PyArray_SelectkindConverter': 298, numpy/core/src/multiarray/conversion_utils.c:PyArray_SelectkindConverter(PyObject *obj, NPY_SELECTKIND *selectkind) numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, Here I don't see PyArray_SelectkindConverter in conversion_utils.h as you said it is present. Witch commit do you use? It's not there, it is part of the API. I've got a PR to add it to the *.h file. The question is why you are the only person (so far) to have a problem compiling. What are your CFLAGS? Chuck Fred On Mon, Sep 9, 2013 at 11:02 AM, Charles R Harris charlesr.har...@gmail.com mailto:charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 8:51 AM, Charles R Harris charlesr.har...@gmail.com mailto:charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.org mailto:no...@nouiz.org wrote: 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
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
I tried it and retried and it still fail. This is in an virtualenv $git show commit c9b06111227f7a4ec213571f97e1b8d19b9c23f5 Merge: 73fbfb2 8edccea Author: Charles Harris charlesr.har...@gmail.com Date: Sun Sep 8 19:47:21 2013 -0700 Merge pull request #3701 from cgohlke/patch-2 ENH: add support for Python 3.4 ast.NameConstant $rm -rf build ## Fail as there is no such directory $pip install . # fail with the same error $pip uninstall numpy $python setup.py install --user # fail with the same error $pip install . ## fail with the same error: $git grep PyArray_SelectkindConverter doc/release/1.8.0-notes.rst:* PyArray_SelectkindConverter numpy/core/code_generators/numpy_api.py: 'PyArray_SelectkindConverter': 298, numpy/core/src/multiarray/conversion_utils.c:PyArray_SelectkindConverter(PyObject *obj, NPY_SELECTKIND *selectkind) numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, numpy/core/src/multiarray/methods.c: PyArray_SelectkindConverter, sortkind, Here I don't see PyArray_SelectkindConverter in conversion_utils.h as you said it is present. Witch commit do you use? Fred On Mon, Sep 9, 2013 at 11:02 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 8:51 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.org wrote: 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? No, it looks like a bug. What is strange is that it doesn't show up on my machine. What compiler flags are you using? Could you make a PR for this? snip Wait a minute, it is in the API. Try a clean build and see what happens. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: 1.8.0b2 release.
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 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
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'
In case it is useful: there are a few failures in the scipy.io.matlab
and scipy.fftpack modules when testing scipy 0.12.0 (built against numpy
1.7.1) with numpy 1.8.0b2. I have not looked in detail.
On Python 3.3 only, 32 and 64 bit:
==
ERROR: test_mio.test_str_round
--
Traceback (most recent call last):
File X:\Python33-x32\lib\site-packages\nose\case.py, line 198, in
runTest
self.test(*self.arg)
File
X:\Python33-x32\lib\site-packages\scipy\io\matlab\tests\test_mio.py,
line 923, in test_str_round
savemat_future(stream, dict(a=in_from_str))
File X:\Python33-x32\lib\site-packages\scipy\io\matlab\mio.py, line
270, in savemat
MW.put_variables(mdict)
File X:\Python33-x32\lib\site-packages\scipy\io\matlab\mio5.py,
line 866, in put_variables
self._matrix_writer.write_top(var, asbytes(name), is_global)
File X:\Python33-x32\lib\site-packages\scipy\io\matlab\mio5.py,
line 617, in write_top
self.write(arr)
File X:\Python33-x32\lib\site-packages\scipy\io\matlab\mio5.py,
line 652, in write
self.write_char(narr, codec)
File X:\Python33-x32\lib\site-packages\scipy\io\matlab\mio5.py,
line 698, in write_char
arr = arr_to_chars(arr)
File X:\Python33-x32\lib\site-packages\scipy\io\matlab\miobase.py,
line 392, in arr_to_chars
buffer=arr)
ValueError: ndarray is not C-contiguous
On Python 2.7 only, 32 and 64 bit (this kind of error also occurs in the
tests of pytables 3.3):
==
ERROR: test_mio.test_load('unicode',
['X:\\Python27\\lib\\site-packages\\scipy\\io\\matlab\\tests\\data\\testunicode_7.1
_GLNX86.mat',
'X:\\Python27\\lib\\site-packages\\scipy\\io\\matlab\\tests\\data\\testunicode_7.4_GLNX86.mat'],
{'testuni
code': array([ u'Japanese:
\n\u3059\u3079\u3066\u306e\u4eba\u9593\u306f\u3001\u751f\u307e\u308c\u306a\u304c\u3089\u306b\
u3057\u3066\u81ea\u7531\u3067\u3042\u308a\u3001\n\u304b\u3064\u3001\u5c0a\u53b3\u3068\u6a29\u5229\u3068
\u306b\u3064\u30
44\u3066\u5e73\u7b49\u3067\u3042\u308b\u3002\n\u4eba\u9593\u306f\u3001\u7406\u6027\u3068\u826f\u5fc3\u3068\u3092\u6388\u
3051\u3089\u308c\u3066\u304a\u308a\u3001\n\u4e92\u3044\u306b\u540c\u80de\u306e\u7cbe\u795e\u3092\u3082\u3063\u3066\u884c
\u52d5\u3057\u306a\u3051\u308c\u3070\u306a\u3089\u306a\u3044\u3002'],
--
Traceback (most recent call last):
File X:\Python27\lib\site-packages\nose\case.py, line 197, in runTest
self.test(*self.arg)
File
X:\Python27\lib\site-packages\scipy\io\matlab\tests\test_mio.py, line
314, in _load_check_case
matdict = loadmat(file_name, struct_as_record=True)
File X:\Python27\lib\site-packages\scipy\io\matlab\mio.py, line
176, in loadmat
matfile_dict = MR.get_variables(variable_names)
File X:\Python27\lib\site-packages\scipy\io\matlab\mio5.py, line
294, in get_variables
res = self.read_var_array(hdr, process)
File X:\Python27\lib\site-packages\scipy\io\matlab\mio5.py, line
257, in read_var_array
return
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Sun, Sep 8, 2013 at 3:45 PM, Christoph Gohlke cgoh...@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
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: 1.8.0b2 release.
On Sun, Sep 8, 2013 at 6:36 PM, Charles R Harris
charlesr.har...@gmail.comwrote:
On Sun, Sep 8, 2013 at 3:45 PM, Christoph Gohlke cgoh...@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@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
