Numpy 1.10.4 release.

Hi All, I'm pleased the release of the Numpy 1.10.4 (bugs stomped) release. This release was motivated by a reported segfault, but a few additional fixes were made: * gh-6922 BUG: numpy.recarray.sort segfaults on Windows, * gh-6937 BUG: busday_offset does the wrong thing with modifiedpreceding roll, * gh-6949 BUG: Type is lost when slicing a subclass of recarray, together with one minor enhancement * gh-6950 BUG trace is not subclass aware, np.trace(ma) != ma.trace(). The sources and documentation are available on Sourceforge, but no binaries. The usual windows binaries were ommitted due to problems with the toolchain. We hope that will be remedied in the future. Mac binaries can be installed from pypi. "Where is numpy 1.10.3?", you may ask. There were glitches with the uploads to pypi for that version that necessitated a version upgrade. A release manager's life is not a happy one. Many thanks to Marten van Kerkwijk, Sebastian Seberg, and Mark Wiebe for the quick bug fixes. Chuck

On Thu, Jan 7, 2016 at 1:39 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
"Where is numpy 1.10.3?", you may ask. There were glitches with the uploads to pypi for that version that necessitated a version upgrade. A release manager's life is not a happy one.
Ah, okay, I was confused about that when I pip installed Numpy just a few minutes ago :) Has the Numpy project opted to not do .postN releases? I'm curious since I had to do one of these for Astropy recently and it was not the most pleasant experience... Anyways thanks for the release! Erik

On Thu, Jan 7, 2016 at 12:01 PM, Erik Bray <erik.m.bray+numpy@gmail.com> wrote:
On Thu, Jan 7, 2016 at 1:39 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
"Where is numpy 1.10.3?", you may ask. There were glitches with the uploads to pypi for that version that necessitated a version upgrade. A release manager's life is not a happy one.
Ah, okay, I was confused about that when I pip installed Numpy just a few minutes ago :)
Has the Numpy project opted to not do .postN releases? I'm curious since I had to do one of these for Astropy recently and it was not the most pleasant experience...
Yes, we opted out after an experience of trying to fix up the 1.10.0 release uploads (not signed) with a `.post1` release. The main problem for us was that NumpyVersion did not deal with that form, plus pypi went ahead and created a new release, so it was simpler to just make a real new release.
Anyways thanks for the release!
I confess to being a bit nervous about not making an rc release. Of course, no one tests those anyway ;) Let us know how things work out. Chuck
participants (2)
-
Charles R Harris
-
Erik Bray