
Hi,
I am pleased to announce the availability of NumPy 1.5.1. This bug-fix release comes almost 3 months after the 1.5.0 release, it contains no new features compared to 1.5.0.
Binaries, sources and release notes can be found at https://sourceforge.net/projects/numpy/files/.
Thank you to everyone who contributed to this release.
Enjoy, The numpy developers.
========================= NumPy 1.5.1 Release Notes =========================
Numpy 1.5.1 is a bug-fix release with no new features compared to 1.5.0.
Numpy source code location changed ==================================
Numpy has stopped using SVN as the version control system, and moved to Git. The development source code for Numpy can from now on be found at
Note on GCC versions ====================
On non-x86 platforms, Numpy can trigger a bug in the recent GCC compiler versions 4.5.0 and 4.5.1: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45967 We recommend not using these versions of GCC for compiling Numpy on these platforms.
Bugs fixed ==========
Of the following, #1605 is important for Cython modules.
- #937: linalg: lstsq should always return real residual - #1196: lib: fix negative indices in s_ and index_exp - #1287: core: fix uint64 -> Python int cast - #1491: core: richcompare should return Py_NotImplemented when undefined - #1517: lib: close file handles after use in numpy.lib.npyio.* - #1605: core: ensure PEP 3118 buffers can be released in exception handler - #1617: core: fix clongdouble cast to Python complex() - #1625: core: fix detection for ``isfinite`` routine - #1626: core: fix compilation with Solaris 10 / Sun Studio 12.1
Scipy could not be built against Numpy 1.5.0 on OS X due to a numpy.distutils bug, #1399. This issue is fixed now.
- #1399: distutils: use C arch flags for Fortran compilation on OS X.
Python 3 specific; #1610 is important for any I/O:
- #----: f2py: make f2py script runnable on Python 3 - #1604: distutils: potential infinite loop in numpy.distutils - #1609: core: use accelerated BLAS, when available - #1610: core: ensure tofile and fromfile maintain file handle positions
Checksums =========
b3db7d1ccfc3640b4c33b7911dbceabc release/installers/numpy-1.5.1-py2.5-python.org-macosx10.3.dmg 55f5863856485bbb005b77014edcd34a release/installers/numpy-1.5.1-py2.6-python.org-macosx10.3.dmg 420113e2a30712668445050a0f38e7a6 release/installers/numpy-1.5.1-py2.7-python.org-macosx10.3.dmg 757885ab8d64cf060ef629800da2e65c release/installers/numpy-1.5.1-py2.7-python.org-macosx10.5.dmg 11e60c3f7f3c86fcb5facf88c3981fd3 release/installers/numpy-1.5.1-win32-superpack-python2.5.exe 3fc14943dc2fcf740d8c204455e68aa7 release/installers/numpy-1.5.1-win32-superpack-python2.6.exe a352acce86c8b2cfb247e38339e27fd0 release/installers/numpy-1.5.1-win32-superpack-python2.7.exe 160de9794e4a239c9da1196a5eb30f7e release/installers/numpy-1.5.1-win32-superpack-python3.1.exe 376ef150df41b5353944ab742145352d release/installers/numpy-1.5.1.tar.gz ab6045070c0de5016fdf94dd2a79638b release/installers/numpy-1.5.1.zip

On 11/20/10 11:04 PM, Ralf Gommers wrote:
I am pleased to announce the availability of NumPy 1.5.1.
Binaries, sources and release notes can be found at https://sourceforge.net/projects/numpy/files/.
Thank you to everyone who contributed to this release.
Yes, thanks so much -- in particular thanks to the team that build the OS-X binaries -- looks like a complete set!
-Chris

Hi,
On Mon, Nov 22, 2010 at 11:35 AM, Christopher Barker Chris.Barker@noaa.gov wrote:
On 11/20/10 11:04 PM, Ralf Gommers wrote:
I am pleased to announce the availability of NumPy 1.5.1.
Binaries, sources and release notes can be found at https://sourceforge.net/projects/numpy/files/.
Thank you to everyone who contributed to this release.
Yes, thanks so much -- in particular thanks to the team that build the OS-X binaries -- looks like a complete set!
Many thanks from me too - particularly for clearing up that annoying numpy-distuils scipy build problem.
Cheers,
Matthew

On Tue, Nov 23, 2010 at 3:35 AM, Christopher Barker Chris.Barker@noaa.govwrote:
On 11/20/10 11:04 PM, Ralf Gommers wrote:
I am pleased to announce the availability of NumPy 1.5.1.
Binaries, sources and release notes can be found at
https://sourceforge.net/projects/numpy/files/.
Thank you to everyone who contributed to this release.
Yes, thanks so much -- in particular thanks to the team that build the OS-X binaries -- looks like a complete set!
It does look like a complete set. And it was named correctly and in sync
with python.org for a single week. From pythonmac list:
"With Python 2.7, there are two Mac OS X installer variants available for download: the "traditional" 32-bit-only (Intel and PPC) version that installs and runs on all versions of OS X from 10.3.9 through current 10.6.x; and a new 64-bit/32-bit (Intel only) variant. As discussed in http://bugs.python.org/issue9227, there were problems using Tkinter and IDLE with the original 2.7 64/32 installer. The problem is that the only supported non-X11 64-bit Tcl/Tk at the moment is the one supplied by Apple in 10.6 and the installer tried unsuccessfully to support both 10.5 and 10.6. For 2.7.1, the 64/32 installer now only supports 10.6.x and will only use the Apple-supplied Tcl/Tk 8.5. The 32-bit-only installer is still built to link with either an Active/State Tcl/Tk 8.4, if installed in /Library/Frameworks, or fallback to the Apple-supplied Tcl/Tk 8.4 in OS X 10.4 through 10.6."
So for the next release we'll build the 10.6 binary on 10.6 again. Sigh.
Ralf

Hi Ralf,
2010/12/5 Ralf Gommers ralf.gommers@googlemail.com:
It does look like a complete set. And it was named correctly and in sync with python.org for a single week. From pythonmac list:
"With Python 2.7, there are two Mac OS X installer variants available for download: the "traditional" 32-bit-only (Intel and PPC) version that installs and runs on all versions of OS X from 10.3.9 through current 10.6.x; and a new 64-bit/32-bit (Intel only) variant. As discussed in http://bugs.python.org/issue9227, there were problems using Tkinter and IDLE with the original 2.7 64/32 installer. The problem is that the only supported non-X11 64-bit Tcl/Tk at the moment is the one supplied by Apple in 10.6 and the installer tried unsuccessfully to support both 10.5 and 10.6. For 2.7.1, the 64/32 installer now only supports 10.6.x and will only use the Apple-supplied Tcl/Tk 8.5. The 32-bit-only installer is still built to link with either an Active/State Tcl/Tk 8.4, if installed in /Library/Frameworks, or fallback to the Apple-supplied Tcl/Tk 8.4 in OS X 10.4 through 10.6."
So for the next release we'll build the 10.6 binary on 10.6 again. Sigh.
But the i386/ppc version should still be built on 10.5?
Shall I give you commit rights on my repo for the build logs (concerning the i386/x86_64 10.6 build)?
Who is going to do the 10.6 builds?
Friedrich

On Sun, Dec 5, 2010 at 8:33 PM, Friedrich Romstedt < friedrichromstedt@gmail.com> wrote:
Hi Ralf,
2010/12/5 Ralf Gommers ralf.gommers@googlemail.com:
It does look like a complete set. And it was named correctly and in sync with python.org for a single week. From pythonmac list:
"With Python 2.7, there are two Mac OS X installer variants available for download: the "traditional" 32-bit-only (Intel and PPC) version that installs and runs on all versions of OS X from 10.3.9 through current 10.6.x; and a new 64-bit/32-bit (Intel only) variant. As discussed in http://bugs.python.org/issue9227, there were problems using Tkinter and IDLE with the original 2.7 64/32 installer. The problem is that the only supported non-X11 64-bit Tcl/Tk at the moment is the one supplied by Apple in 10.6 and the installer tried unsuccessfully to support both 10.5 and 10.6. For 2.7.1, the 64/32 installer now only supports 10.6.x and will only use the Apple-supplied Tcl/Tk 8.5. The 32-bit-only installer is still built to link with either an Active/State Tcl/Tk 8.4, if installed in /Library/Frameworks, or fallback to the Apple-supplied Tcl/Tk 8.4 in OS X 10.4 through 10.6."
So for the next release we'll build the 10.6 binary on 10.6 again. Sigh.
But the i386/ppc version should still be built on 10.5?
Yes.
Shall I give you commit rights on my repo for the build logs (concerning the i386/x86_64 10.6 build)?
Sure.
Who is going to do the 10.6 builds?
I'll do that one.
Cheers, Ralf
participants (4)
-
Christopher Barker
-
Friedrich Romstedt
-
Matthew Brett
-
Ralf Gommers