[Numpy-discussion] ANN: NumPy 1.7.1rc1 release

Ondřej Čertík ondrej.certik@gmail....
Tue Mar 26 19:32:06 CDT 2013


On Sun, Mar 24, 2013 at 8:00 PM, Charles R Harris
<charlesr.harris@gmail.com> wrote:
>
>
> On Sun, Mar 24, 2013 at 3:02 PM, Ondřej Čertík <ondrej.certik@gmail.com>
> wrote:
>>
>> Hi,
>>
>> I'm pleased to announce the availability of the first release candidate of
>> NumPy 1.7.1rc1.
>>
>> Sources and binary installers can be found at
>> https://sourceforge.net/projects/numpy/files/NumPy/1.7.1rc1/
>>
>> Please test it and report any bugs. It fixes a few bugs, listed below.
>>
>> I would like to thank everybody who contributed patches to this release:
>> Nathaniel J. Smith, Sebastian Berg, Charles Harris, Bradley M. Froehle,
>> Ralf Gommers, Christoph Gohlke, Mark Wiebe and Maximilian Albert.
>>
>> Cheers,
>> Ondrej
>>
>>
>>
>> =========================
>> NumPy 1.7.1 Release Notes
>> =========================
>>
>> This is a bugfix only release in the 1.7.x series.
>>
>>
>> Issues fixed
>> ------------
>>
>> gh-2973   Fix `1` is printed during numpy.test()
>> gh-2983   BUG: gh-2969: Backport memory leak fix 80b3a34.
>> gh-3007   Backport gh-3006
>> gh-2984   Backport fix complex polynomial fit
>> gh-2982   BUG: Make nansum work with booleans.
>> gh-2985   Backport large sort fixes
>> gh-3039   Backport object take
>> gh-3105   Backport nditer fix op axes initialization
>> gh-3108   BUG: npy-pkg-config ini files were missing after Bento build.
>> gh-3124   BUG: PyArray_LexSort allocates too much temporary memory.
>> gh-3131   BUG: Exported f2py_size symbol prevents linking multiple f2py
>> modules.
>> gh-3117   Backport gh-2992
>> gh-3135   DOC: Add mention of PyArray_SetBaseObject stealing a reference
>> gh-3134   DOC: Fix typo in fft docs (the indexing variable is 'm', not
>> 'n').
>> gh-3136   Backport #3128
>>
>> Checksums
>> =========
>>
>> 28c3f3e71b5eaa6bfab6e8340dbd35e7  release/installers/numpy-1.7.1rc1.tar.gz
>> 436f416dee10d157314bd9da7ab95c9c
>> release/installers/numpy-1.7.1rc1-win32-superpack-python2.7.exe
>> a543c8cf69f66ff2b4c9565646105863
>> release/installers/numpy-1.7.1rc1-win32-superpack-python2.6.exe
>> 6dfcbbd449b7fe4e841c5fd1bfa7af7c
>> release/installers/numpy-1.7.1rc1-win32-superpack-python2.5.exe
>> 22912792a1b6155ae2bdbc30bee8fadc
>> release/installers/numpy-1.7.1rc1-win32-superpack-python3.2.exe
>> 95bc5a5fcce9fcbc2717a774dccae31b
>> release/installers/numpy-1.7.1rc1-win32-superpack-python3.3.exe
>> 33cf283765a148846b49b89fb96d67d5
>> release/installers/numpy-1.7.1rc1-win32-superpack-python3.1.exe
>> 9761de4b35493fed38c5d177da9c3b37  release/installers/numpy-1.7.1rc1.zip
>> __
>
>
> Great. The fix for the memory leak should make some folks happy.

Yes. I created an issue here for them to test it:

https://github.com/scikit-learn/scikit-learn/issues/1809

Just to make sure.

Ondrej


More information about the NumPy-Discussion mailing list