Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sun, May 13, 2012 at 1:14 PM, Paul Anton Letnes
paul.anton.let...@gmail.com wrote:
On Sat, May 12, 2012 at 9:50 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, May 6, 2012 at 12:12 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes
paul.anton.let...@gmail.com wrote:
Hi,
I'm getting a couple of errors when testing. System:
Arch Linux (updated today)
Python 3.2.3
gcc 4.7.0
(Anything else?)
I think that this error:
AssertionError: selectedrealkind(19): expected -1 but got 16
is due to the fact that newer versions of gfortran actually supports
precision this high (quad precision).
Yes, but it should be fixed. I can't duplicate this here with a fresh
checkout of the branch.
This failure makes no sense to me.
Error comes from this code:
'selectedrealkind(%s): expected %r but got %r' % (i,
selected_real_kind(i), selectedrealkind(i)))
So selected_real_kind(19) returns -1.
selected_real_kind is the function
numpy.f2py.crackfortran._selected_real_kind_func, which is defined as:
def _selected_real_kind_func(p, r=0, radix=0):
#XXX: This should be processor dependent
# This is only good for 0 = p = 20
if p 7: return 4
if p 16: return 8
if platform.machine().lower().startswith('power'):
if p = 20:
return 16
else:
if p 19:
return 10
elif p = 20:
return 16
return -1
For p=19 this function should always return 16. So the result from
compiling
foo.f90 is fine, but the test is broken in a very strange way.
Paul, is the failure reproducible on your machine? If so, can you try to
debug it?
Ralf
Hi Ralf.
The Arch numpy (1.6.1) for python 2.7, installed via pacman (the
package manager) has this problem.
After installation of numpy 1.6.2rc1 in a virtualenv, the test passes.
Maybe the bug was fixed in the RC, and I screwed up which numpy
version I tested? I'm sorry that I can't find out - I just built a new
machine, and the old one is lying around the livingroom in pieces. Was
that particular bit of code changed between 1.6.1 and 1.6.2rc1?
It was actually, in https://github.com/numpy/numpy/commit/e7f2210e1.
So you tested 1.6.1 by accident before, and it's working now? Problem
solved in that case.
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Mon, May 14, 2012 at 9:47 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, May 13, 2012 at 1:14 PM, Paul Anton Letnes
paul.anton.let...@gmail.com wrote:
On Sat, May 12, 2012 at 9:50 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, May 6, 2012 at 12:12 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes
paul.anton.let...@gmail.com wrote:
Hi,
I'm getting a couple of errors when testing. System:
Arch Linux (updated today)
Python 3.2.3
gcc 4.7.0
(Anything else?)
I think that this error:
AssertionError: selectedrealkind(19): expected -1 but got 16
is due to the fact that newer versions of gfortran actually supports
precision this high (quad precision).
Yes, but it should be fixed. I can't duplicate this here with a fresh
checkout of the branch.
This failure makes no sense to me.
Error comes from this code:
'selectedrealkind(%s): expected %r but got %r' % (i,
selected_real_kind(i), selectedrealkind(i)))
So selected_real_kind(19) returns -1.
selected_real_kind is the function
numpy.f2py.crackfortran._selected_real_kind_func, which is defined as:
def _selected_real_kind_func(p, r=0, radix=0):
#XXX: This should be processor dependent
# This is only good for 0 = p = 20
if p 7: return 4
if p 16: return 8
if platform.machine().lower().startswith('power'):
if p = 20:
return 16
else:
if p 19:
return 10
elif p = 20:
return 16
return -1
For p=19 this function should always return 16. So the result from
compiling
foo.f90 is fine, but the test is broken in a very strange way.
Paul, is the failure reproducible on your machine? If so, can you try to
debug it?
Ralf
Hi Ralf.
The Arch numpy (1.6.1) for python 2.7, installed via pacman (the
package manager) has this problem.
After installation of numpy 1.6.2rc1 in a virtualenv, the test passes.
Maybe the bug was fixed in the RC, and I screwed up which numpy
version I tested? I'm sorry that I can't find out - I just built a new
machine, and the old one is lying around the livingroom in pieces. Was
that particular bit of code changed between 1.6.1 and 1.6.2rc1?
It was actually, in https://github.com/numpy/numpy/commit/e7f2210e1.
So you tested 1.6.1 by accident before, and it's working now? Problem solved
in that case.
Ralf
Looks like it to me! Sorry for the silly bug report. I'll have to take
more care next time...
Paul
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 12, 2012 at 9:50 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, May 6, 2012 at 12:12 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes
paul.anton.let...@gmail.com wrote:
Hi,
I'm getting a couple of errors when testing. System:
Arch Linux (updated today)
Python 3.2.3
gcc 4.7.0
(Anything else?)
I think that this error:
AssertionError: selectedrealkind(19): expected -1 but got 16
is due to the fact that newer versions of gfortran actually supports
precision this high (quad precision).
Yes, but it should be fixed. I can't duplicate this here with a fresh
checkout of the branch.
This failure makes no sense to me.
Error comes from this code:
'selectedrealkind(%s): expected %r but got %r' % (i,
selected_real_kind(i), selectedrealkind(i)))
So selected_real_kind(19) returns -1.
selected_real_kind is the function
numpy.f2py.crackfortran._selected_real_kind_func, which is defined as:
def _selected_real_kind_func(p, r=0, radix=0):
#XXX: This should be processor dependent
# This is only good for 0 = p = 20
if p 7: return 4
if p 16: return 8
if platform.machine().lower().startswith('power'):
if p = 20:
return 16
else:
if p 19:
return 10
elif p = 20:
return 16
return -1
For p=19 this function should always return 16. So the result from compiling
foo.f90 is fine, but the test is broken in a very strange way.
Paul, is the failure reproducible on your machine? If so, can you try to
debug it?
Ralf
Hi Ralf.
The Arch numpy (1.6.1) for python 2.7, installed via pacman (the
package manager) has this problem.
After installation of numpy 1.6.2rc1 in a virtualenv, the test passes.
Maybe the bug was fixed in the RC, and I screwed up which numpy
version I tested? I'm sorry that I can't find out - I just built a new
machine, and the old one is lying around the livingroom in pieces. Was
that particular bit of code changed between 1.6.1 and 1.6.2rc1?
Paul
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Tue, May 8, 2012 at 3:23 PM, Derek Homeier de...@astro.physik.uni-goettingen.de wrote: On 06.05.2012, at 8:16AM, Paul Anton Letnes wrote: All tests for 1.6.2rc1 pass on Mac OS X 10.7.3 python 2.7.2 gcc 4.2 (Apple) Passing as well on 10.6 x86_64 and on 10.5.8 ppc with python 2.5.6/2.6.6/2.7.2 Apple gcc 4.0.1, but I am getting one failure on Lion (same with Python 2.5.6+2.6.7): Python version 2.7.3 (default, May 6 2012, 15:05:35) [GCC 4.2.1 Compatible Apple Clang 3.0 (tags/Apple/clang-211.12)] nose version 1.1.2 == FAIL: Test basic arithmetic function errors -- Traceback (most recent call last): File /sw/lib/python2.7/site-packages/numpy/testing/decorators.py, line 215, in knownfailer return f(*args, **kwargs) File /sw/lib/python2.7/site-packages/numpy/core/tests/test_numeric.py, line 323, in test_floating_exceptions lambda a,b:a*b, ft_tiny, ft_tiny) File /sw/lib/python2.7/site-packages/numpy/core/tests/test_numeric.py, line 271, in assert_raises_fpe Type %s did not raise fpe error '%s'. % (ftype, fpeerr)) File /sw/lib/python2.7/site-packages/numpy/testing/utils.py, line 34, in assert_ raise AssertionError(msg) AssertionError: Type type 'numpy.complex64' did not raise fpe error ''. test_floating_exceptions and test_floating_exceptions_power keep on failing on a number of different platform/compiler combinations. It's http://projects.scipy.org/numpy/ticket/1755. It's quite hard to find the issue. I propose to just mark these as knownfail unconditionally in both 1.6.x and master. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 11:06 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes paul.anton.let...@gmail.com wrote: Hi, I'm getting a couple of errors when testing. System: Arch Linux (updated today) Python 3.2.3 gcc 4.7.0 (Anything else?) I think that this error: AssertionError: selectedrealkind(19): expected -1 but got 16 is due to the fact that newer versions of gfortran actually supports precision this high (quad precision). Cheers Paul python -c 'import numpy;numpy.test(full)' Running unit tests for numpy NumPy version 1.6.1 NumPy is installed in /usr/lib/python3.2/site-packages/numpy Python version 3.2.3 (default, Apr 23 2012, 23:35:30) [GCC 4.7.0 20120414 (prerelease)] nose version 1.1.2 S.S..SSS...KK.K.K..K..F../usr/lib/python3.2/site-packages/numpy/lib/format.py:575: ResourceWarning: unclosed file _io.BufferedReader name='/tmp/tmpmkxhkq' mode=mode, offset=offset) /usr/lib/python3.2/subprocess.py:471: ResourceWarning: unclosed file _io.FileIO name=3 mode='rb' return Popen(*popenargs, **kwargs).wait() /usr/lib/python3.2/subprocess.py:471: ResourceWarning: unclosed file _io.FileIO name=7 mode='rb' return Popen(*popenargs, **kwargs).wait() ..F... == FAIL: test_kind.TestKind.test_all -- Traceback (most
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
Hello, On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. ... BLD: add support for the new X11 directory structure on Ubuntu co. We've just discovered that this fix is not enough. Actually the new directories are due to the multi-arch feature of Debian systems, that allows to install libraries from other (foreign) architectures than the one the machine is (the classic example, i386 libraries on a amd64 host). the fix included to look up in additional directories is currently only for X11, while for example Debian has fftw3 that's multi-arch-ified and thus will fail to be detected. Could this fix be extended to include all other things that are checked? for reference the bug in Debian is [1]; there was also a patch[2] in previous versions, that was using gcc to get the multi-arch paths - you might use as a reference, or to implement something debian-systems-specific. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640940 [2] http://anonscm.debian.org/viewvc/python-modules/packages/numpy/trunk/debian/patches/50_search-multiarch-paths.patch?view=markuppathrev=21168 It would be awesome is such support would end up in 1.6.2 . Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 12, 2012 at 6:22 PM, Sandro Tosi matrixh...@gmail.com wrote: Hello, On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. ... BLD: add support for the new X11 directory structure on Ubuntu co. We've just discovered that this fix is not enough. Actually the new directories are due to the multi-arch feature of Debian systems, that allows to install libraries from other (foreign) architectures than the one the machine is (the classic example, i386 libraries on a amd64 host). the fix included to look up in additional directories is currently only for X11, while for example Debian has fftw3 that's multi-arch-ified and thus will fail to be detected. Could this fix be extended to include all other things that are checked? for reference the bug in Debian is [1]; there was also a patch[2] in previous versions, that was using gcc to get the multi-arch paths - you might use as a reference, or to implement something debian-systems-specific. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640940 [2] http://anonscm.debian.org/viewvc/python-modules/packages/numpy/trunk/debian/patches/50_search-multiarch-paths.patch?view=markuppathrev=21168 It would be awesome is such support would end up in 1.6.2 . Hardcoding some more paths to check in distutils/system_info.py should be OK, also for 1.6.2 (will require a new RC). The --print-multiarch thing looks very questionable. As far as I can tell, it's a Debian specific gcc patch, only available in gcc 4.6 and up. Ubuntu before 11.10 release also doesn't have it. Therefore I don't think use of --print-multiarch is appropriate for numpy for now, and certainly not a change I'd like to make to distutils right before a release. If anyone with access to a Debian/Ubuntu system could come up with a patch which adds the right paths to system_info.py, that would be great. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sun, May 6, 2012 at 12:12 AM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes
paul.anton.let...@gmail.com wrote:
Hi,
I'm getting a couple of errors when testing. System:
Arch Linux (updated today)
Python 3.2.3
gcc 4.7.0
(Anything else?)
I think that this error:
AssertionError: selectedrealkind(19): expected -1 but got 16
is due to the fact that newer versions of gfortran actually supports
precision this high (quad precision).
Yes, but it should be fixed. I can't duplicate this here with a fresh
checkout of the branch.
This failure makes no sense to me.
Error comes from this code:
'selectedrealkind(%s): expected %r but got %r' % (i,
selected_real_kind(i), selectedrealkind(i)))
So selected_real_kind(19) returns -1.
selected_real_kind is the function
numpy.f2py.crackfortran._selected_real_kind_func, which is defined as:
def _selected_real_kind_func(p, r=0, radix=0):
#XXX: This should be processor dependent
# This is only good for 0 = p = 20
if p 7: return 4
if p 16: return 8
if platform.machine().lower().startswith('power'):
if p = 20:
return 16
else:
if p 19:
return 10
elif p = 20:
return 16
return -1
For p=19 this function should always return 16. So the result from
compiling foo.f90 is fine, but the test is broken in a very strange way.
Paul, is the failure reproducible on your machine? If so, can you try to
debug it?
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On 05/05/2012 12:15 PM, Ralf Gommers wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Built fine in Fedora Rawhide (F18). Ran 3210 tests in 17.036s OK (KNOWNFAIL=3, SKIP=1) Running unit tests for numpy NumPy version 1.6.2rc1 NumPy is installed in /builddir/build/BUILDROOT/numpy-1.6.2-0.1.rc1.fc18.x86_64/usr/lib64/python2.7/site-packages/numpy Python version 2.7.3 (default, Apr 30 2012, 20:31:33) [GCC 4.7.0 20120416 (Red Hat 4.7.0-2)] nose version 1.1.2 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 2:15 PM, Ralf Gommers ralf.gomm...@googlemail.comwrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Cheers, Ralf ``numpy.core`` issues fixed --- #2063 make unique() return consistent index #1138 allow creating arrays from empty buffers or empty slices #1446 correct note about correspondence vstack and concatenate #1149 make argmin() work for datetime #1672 fix allclose() to work for scalar inf #1747 make np.median() work for 0-D arrays #1776 make complex division by zero to yield inf properly #1675 add scalar support for the format() function #1905 explicitly check for NaNs in allclose() #1952 allow floating ddof in std() and var() #1948 fix regression for indexing chararrays with empty list #2017 fix type hashing #2046 deleting array attributes causes segfault #2033 a**2.0 has incorrect type #2045 make attribute/iterator_element deletions not segfault #2021 fix segfault in searchsorted() #2073 fix float16 __array_interface__ bug ``numpy.lib`` issues fixed -- #2048 break reference cycle in NpzFile #1573 savetxt() now handles complex arrays #1387 allow bincount() to accept empty arrays #1899 fixed histogramdd() bug with empty inputs #1793 fix failing npyio test under py3k #1936 fix extra nesting for subarray dtypes #1848 make tril/triu return the same dtype as the original array #1918 use Py_TYPE to access ob_type, so it works also on Py3 ``numpy.f2py`` changes -- ENH: Introduce new options extra_f77_compiler_args and extra_f90_compiler_args BLD: Improve reporting of fcompiler value BUG: Fix f2py test_kind.py test ``numpy.poly`` changes -- ENH: Add some tests for polynomial printing ENH: Add companion matrix functions DOC: Rearrange the polynomial documents BUG: Fix up links to classes DOC: Add version added to some of the polynomial package modules DOC: Document xxxfit functions in the polynomial package modules BUG: The polynomial convenience classes let different types interact DOC: Document the use of the polynomial convenience classes DOC: Improve numpy reference documentation of polynomial classes ENH: Improve the computation of polynomials from roots STY: Code cleanup in polynomial [*]fromroots functions DOC: Remove references to cast and NA, which were added in 1.7 ``numpy.distutils`` issues fixed --- #1261 change compile flag on AIX from -O5 to -O3 #1377 update HP compiler flags #1383 provide better support for C++ code on HPUX #1857 fix build for py3k + pip BLD: raise a clearer warning in case of building without cleaning up first BLD: follow build_ext coding convention in build_clib BLD: fix up detection of Intel CPU on OS X in system_info.py BLD: add support for the new X11 directory structure on Ubuntu co. BLD: add ufsparse to the libraries search path. BLD: add 'pgfortran' as a valid compiler in the Portland Group BLD: update version match regexp for IBM AIX Fortran compilers. I just noticed that my fix for the np.gradient() function isn't listed. https://github.com/numpy/numpy/pull/167 Not critical, but if a second rc is needed for any reason, it would be nice to have that in there. Thanks! Ben Root ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Mh, I can't exactly understand this: $ diff -urNad numpy-1.6.1 numpy-1.6.2rc | diffstat | tail -1 2718 files changed, 390859 deletions(-) does it mean that the only thing the RC has done is to remove a lot of stuff? that's weird because the build process went all just fine and unit tests are passing ... /me confused? -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Wed, May 9, 2012 at 10:36 AM, Sandro Tosi matrixh...@gmail.com wrote: On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Mh, I can't exactly understand this: $ diff -urNad numpy-1.6.1 numpy-1.6.2rc | diffstat | tail -1 2718 files changed, 390859 deletions(-) does it mean that the only thing the RC has done is to remove a lot of stuff? that's weird because the build process went all just fine and unit tests are passing ... /me confused? No, only a few files were changed. Since there are about 1000 files in numpy I suspect you are also counting everything in the build and documentation build directories. If you built inplace, you are also going to pick up *.pyc files and such. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Wed, May 9, 2012 at 6:49 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Wed, May 9, 2012 at 10:36 AM, Sandro Tosi matrixh...@gmail.com wrote: On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Mh, I can't exactly understand this: $ diff -urNad numpy-1.6.1 numpy-1.6.2rc | diffstat | tail -1 2718 files changed, 390859 deletions(-) does it mean that the only thing the RC has done is to remove a lot of stuff? that's weird because the build process went all just fine and unit tests are passing ... /me confused? No, only a few files were changed. Since there are about 1000 files in numpy I suspect you are also counting everything in the build and documentation build directories. If you built inplace, you are also going to pick up *.pyc files and such. sorry i didn't say that: they are the tarballs just extracted. i'd have to recheck again downloading from SF -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Please test this release and report any issues on the numpy-discussion mailing list. I think it's probably nice not to ship pyc in the source tarball: $ find numpy-1.6.2rc1/ -name *.pyc numpy-1.6.2rc1/doc/sphinxext/docscrape.pyc numpy-1.6.2rc1/doc/sphinxext/docscrape_sphinx.pyc numpy-1.6.2rc1/doc/sphinxext/numpydoc.pyc numpy-1.6.2rc1/doc/sphinxext/plot_directive.pyc Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Wed, May 9, 2012 at 12:40 PM, Sandro Tosi matrixh...@gmail.com wrote: On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Please test this release and report any issues on the numpy-discussion mailing list. I think it's probably nice not to ship pyc in the source tarball: $ find numpy-1.6.2rc1/ -name *.pyc numpy-1.6.2rc1/doc/sphinxext/docscrape.pyc numpy-1.6.2rc1/doc/sphinxext/docscrape_sphinx.pyc numpy-1.6.2rc1/doc/sphinxext/numpydoc.pyc numpy-1.6.2rc1/doc/sphinxext/plot_directive.pyc Good point ;) Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
Am 05.05.2012 20:15, schrieb Ralf Gommers: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Cheers, Ralf ``numpy.core`` issues fixed --- #2063 make unique() return consistent index #1138 allow creating arrays from empty buffers or empty slices #1446 correct note about correspondence vstack and concatenate #1149 make argmin() work for datetime #1672 fix allclose() to work for scalar inf #1747 make np.median() work for 0-D arrays #1776 make complex division by zero to yield inf properly #1675 add scalar support for the format() function #1905 explicitly check for NaNs in allclose() #1952 allow floating ddof in std() and var() #1948 fix regression for indexing chararrays with empty list #2017 fix type hashing #2046 deleting array attributes causes segfault #2033 a**2.0 has incorrect type #2045 make attribute/iterator_element deletions not segfault #2021 fix segfault in searchsorted() #2073 fix float16 __array_interface__ bug ``numpy.lib`` issues fixed -- #2048 break reference cycle in NpzFile #1573 savetxt() now handles complex arrays #1387 allow bincount() to accept empty arrays #1899 fixed histogramdd() bug with empty inputs #1793 fix failing npyio test under py3k #1936 fix extra nesting for subarray dtypes #1848 make tril/triu return the same dtype as the original array #1918 use Py_TYPE to access ob_type, so it works also on Py3 ``numpy.f2py`` changes -- ENH: Introduce new options extra_f77_compiler_args and extra_f90_compiler_args BLD: Improve reporting of fcompiler value BUG: Fix f2py test_kind.py test ``numpy.poly`` changes -- ENH: Add some tests for polynomial printing ENH: Add companion matrix functions DOC: Rearrange the polynomial documents BUG: Fix up links to classes DOC: Add version added to some of the polynomial package modules DOC: Document xxxfit functions in the polynomial package modules BUG: The polynomial convenience classes let different types interact DOC: Document the use of the polynomial convenience classes DOC: Improve numpy reference documentation of polynomial classes ENH: Improve the computation of polynomials from roots STY: Code cleanup in polynomial [*]fromroots functions DOC: Remove references to cast and NA, which were added in 1.7 ``numpy.distutils`` issues fixed --- #1261 change compile flag on AIX from -O5 to -O3 #1377 update HP compiler flags #1383 provide better support for C++ code on HPUX #1857 fix build for py3k + pip BLD: raise a clearer warning in case of building without cleaning up first BLD: follow build_ext coding convention in build_clib BLD: fix up detection of Intel CPU on OS X in system_info.py BLD: add support for the new X11 directory structure on Ubuntu co. BLD: add ufsparse to the libraries search path. BLD: add 'pgfortran' as a valid compiler in the Portland Group BLD: update version match regexp for IBM AIX Fortran compilers. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion 1.6.2RC1 builds fine under the following configurations (all of them x86_64): * Ubuntu Lucid 10.4 / Python 2.6.5 / GCC 4.4.3: OK (KNOWNFAIL=3, SKIP=5) * Archlinux (as of today) / Python 3.2.3 / GCC 4.7.0: OK (KNOWNFAIL=5, SKIP=5) * Archlinux (as of today) / Python 2.7.3 / GCC: OK (KNOWNFAIL=3, SKIP=5) Great work! Andreas. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On 06.05.2012, at 8:16AM, Paul Anton Letnes wrote: All tests for 1.6.2rc1 pass on Mac OS X 10.7.3 python 2.7.2 gcc 4.2 (Apple) Passing as well on 10.6 x86_64 and on 10.5.8 ppc with python 2.5.6/2.6.6/2.7.2 Apple gcc 4.0.1, but I am getting one failure on Lion (same with Python 2.5.6+2.6.7): Python version 2.7.3 (default, May 6 2012, 15:05:35) [GCC 4.2.1 Compatible Apple Clang 3.0 (tags/Apple/clang-211.12)] nose version 1.1.2 == FAIL: Test basic arithmetic function errors -- Traceback (most recent call last): File /sw/lib/python2.7/site-packages/numpy/testing/decorators.py, line 215, in knownfailer return f(*args, **kwargs) File /sw/lib/python2.7/site-packages/numpy/core/tests/test_numeric.py, line 323, in test_floating_exceptions lambda a,b:a*b, ft_tiny, ft_tiny) File /sw/lib/python2.7/site-packages/numpy/core/tests/test_numeric.py, line 271, in assert_raises_fpe Type %s did not raise fpe error '%s'. % (ftype, fpeerr)) File /sw/lib/python2.7/site-packages/numpy/testing/utils.py, line 34, in assert_ raise AssertionError(msg) AssertionError: Type type 'numpy.complex64' did not raise fpe error ''. -- Ran 3551 tests in 130.778s FAILED (KNOWNFAIL=3, SKIP=4, failures=1) Cheers, Derek ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
All tests for 1.6.2rc1 pass on Mac OS X 10.7.3 python 2.7.2 gcc 4.2 (Apple) Great! Paul On 6. mai 2012, at 00:12, Charles R Harris wrote: On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes paul.anton.let...@gmail.com wrote: Hi, I'm getting a couple of errors when testing. System: Arch Linux (updated today) Python 3.2.3 gcc 4.7.0 (Anything else?) I think that this error: AssertionError: selectedrealkind(19): expected -1 but got 16 is due to the fact that newer versions of gfortran actually supports precision this high (quad precision). Yes, but it should be fixed. I can't duplicate this here with a fresh checkout of the branch. snip 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: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Great! Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. i've just tested the debian package and it builds fine! The tests print some ResourceWarning with python3.2 but they all pass! Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 12:15 PM, Ralf Gommers ralf.gomm...@googlemail.comwrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Cheers, Ralf ``numpy.core`` issues fixed --- #2063 make unique() return consistent index #1138 allow creating arrays from empty buffers or empty slices #1446 correct note about correspondence vstack and concatenate #1149 make argmin() work for datetime #1672 fix allclose() to work for scalar inf #1747 make np.median() work for 0-D arrays #1776 make complex division by zero to yield inf properly #1675 add scalar support for the format() function #1905 explicitly check for NaNs in allclose() #1952 allow floating ddof in std() and var() #1948 fix regression for indexing chararrays with empty list #2017 fix type hashing #2046 deleting array attributes causes segfault #2033 a**2.0 has incorrect type #2045 make attribute/iterator_element deletions not segfault #2021 fix segfault in searchsorted() #2073 fix float16 __array_interface__ bug ``numpy.lib`` issues fixed -- #2048 break reference cycle in NpzFile #1573 savetxt() now handles complex arrays #1387 allow bincount() to accept empty arrays #1899 fixed histogramdd() bug with empty inputs #1793 fix failing npyio test under py3k #1936 fix extra nesting for subarray dtypes #1848 make tril/triu return the same dtype as the original array #1918 use Py_TYPE to access ob_type, so it works also on Py3 ``numpy.f2py`` changes -- ENH: Introduce new options extra_f77_compiler_args and extra_f90_compiler_args BLD: Improve reporting of fcompiler value BUG: Fix f2py test_kind.py test ``numpy.poly`` changes -- ENH: Add some tests for polynomial printing ENH: Add companion matrix functions DOC: Rearrange the polynomial documents BUG: Fix up links to classes DOC: Add version added to some of the polynomial package modules DOC: Document xxxfit functions in the polynomial package modules BUG: The polynomial convenience classes let different types interact DOC: Document the use of the polynomial convenience classes DOC: Improve numpy reference documentation of polynomial classes ENH: Improve the computation of polynomials from roots STY: Code cleanup in polynomial [*]fromroots functions DOC: Remove references to cast and NA, which were added in 1.7 ``numpy.distutils`` issues fixed --- #1261 change compile flag on AIX from -O5 to -O3 #1377 update HP compiler flags #1383 provide better support for C++ code on HPUX #1857 fix build for py3k + pip BLD: raise a clearer warning in case of building without cleaning up first BLD: follow build_ext coding convention in build_clib BLD: fix up detection of Intel CPU on OS X in system_info.py BLD: add support for the new X11 directory structure on Ubuntu co. BLD: add ufsparse to the libraries search path. BLD: add 'pgfortran' as a valid compiler in the Portland Group BLD: update version match regexp for IBM AIX Fortran compilers. Darn, I missed the omission of the random fix from the notes. I'm no good for spelling either. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
Hi, I'm getting a couple of errors when testing. System: Arch Linux (updated today) Python 3.2.3 gcc 4.7.0 (Anything else?) I think that this error: AssertionError: selectedrealkind(19): expected -1 but got 16 is due to the fact that newer versions of gfortran actually supports precision this high (quad precision). Cheers Paul python -c 'import numpy;numpy.test(full)' Running unit tests for numpy NumPy version 1.6.1 NumPy is installed in /usr/lib/python3.2/site-packages/numpy Python version 3.2.3 (default, Apr 23 2012, 23:35:30) [GCC 4.7.0 20120414 (prerelease)] nose version 1.1.2 S.S..SSS...KK.K.K..K..F../usr/lib/python3.2/site-packages/numpy/lib/format.py:575: ResourceWarning: unclosed file _io.BufferedReader name='/tmp/tmpmkxhkq' mode=mode, offset=offset) /usr/lib/python3.2/subprocess.py:471: ResourceWarning: unclosed file _io.FileIO name=3 mode='rb' return Popen(*popenargs, **kwargs).wait() /usr/lib/python3.2/subprocess.py:471: ResourceWarning: unclosed file _io.FileIO name=7 mode='rb' return Popen(*popenargs, **kwargs).wait() ..F... == FAIL: test_kind.TestKind.test_all -- Traceback (most recent call last): File /usr/lib/python3.2/site-packages/nose/case.py, line 198, in runTest self.test(*self.arg) File /usr/lib/python3.2/site-packages/numpy/f2py/tests/test_kind.py, line 30, in test_all
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes paul.anton.let...@gmail.com wrote: Hi, I'm getting a couple of errors when testing. System: Arch Linux (updated today) Python 3.2.3 gcc 4.7.0 (Anything else?) I think that this error: AssertionError: selectedrealkind(19): expected -1 but got 16 is due to the fact that newer versions of gfortran actually supports precision this high (quad precision). Cheers Paul python -c 'import numpy;numpy.test(full)' Running unit tests for numpy NumPy version 1.6.1 NumPy is installed in /usr/lib/python3.2/site-packages/numpy Python version 3.2.3 (default, Apr 23 2012, 23:35:30) [GCC 4.7.0 20120414 (prerelease)] nose version 1.1.2 S.S..SSS...KK.K.K..K..F../usr/lib/python3.2/site-packages/numpy/lib/format.py:575: ResourceWarning: unclosed file _io.BufferedReader name='/tmp/tmpmkxhkq' mode=mode, offset=offset) /usr/lib/python3.2/subprocess.py:471: ResourceWarning: unclosed file _io.FileIO name=3 mode='rb' return Popen(*popenargs, **kwargs).wait() /usr/lib/python3.2/subprocess.py:471: ResourceWarning: unclosed file _io.FileIO name=7 mode='rb' return Popen(*popenargs, **kwargs).wait() ..F... == FAIL: test_kind.TestKind.test_all -- Traceback (most recent call last): File /usr/lib/python3.2/site-packages/nose/case.py, line 198, in
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On 5/5/2012 11:15 AM, Ralf Gommers wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Cheers, Ralf Thank you and Chuck! The rc builds and tests OK on Windows with msvc9/MKL. There are also no apparent problems with scipy, matplotlib and a number of other packages. One pygame 1.9.2pre test fails; I'll look into it. Christoph ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1
On 5/5/2012 2:51 PM, Christoph Gohlke wrote: On 5/5/2012 11:15 AM, Ralf Gommers wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy 1.7.0, this release contains far more fixes than a regular NumPy bugfix release. It also includes a number of documentation and build improvements. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.6.2rc1/ Please test this release and report any issues on the numpy-discussion mailing list. Cheers, Ralf Thank you and Chuck! The rc builds and tests OK on Windows with msvc9/MKL. There are also no apparent problems with scipy, matplotlib and a number of other packages. One pygame 1.9.2pre test fails; I'll look into it. Just to follow up on the pygame test error: it is due to pygame doing incomplete exception handling when checking for invalid dtypes. Easy to fix. Christoph ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
