[Numpy-discussion] Making a 1.13.2 release
Charles R Harris
charlesr.harris at gmail.com
Thu Jul 6 10:37:36 EDT 2017
On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett <matthew.brett at gmail.com>
> On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris
> <charlesr.harris at gmail.com> wrote:
> > Hi All,
> > I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up
> > fixing #29943 so we can close #9272, but the Python release has been
> > delayed to July 11 (expected). The Python problem means that NumPy
> > with Python 3.6.1 will not run in Python 3.6.0. However, I've also been
> > asked to have a bugfixed version of 1.13 available for Scipy 2017 next
> > At this point it looks like the best thing to do is release 1.13.1
> > with Python 3.6.1 and ask folks to upgrade Python if they have a problem,
> > and then release 1.13.2 as soon as 3.6.2 is released.
> I think this problem only applies to Windows. We might be able to
> downgrade the Appveyor Python 3.6.1 to 3.6.0 for that - I can look
> into it today if it would help.
> While I'm at it - how about switching to OpenBLAS wheels on Windows
> for this release?
Haste makes waste ;) I'd rather put off the move to OpenBlas to 1.14 to
allow more time for it to settle, and compiling against Python 3.6.0 seems
like more work than it is worth, It should be easy to upgrade to 3.6.1 for
those affected once they are aware of the problem, and it should not be too
long before Python 3.6.2 is out. I'll call it the Scipy2017 release.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion