On Thu, Jul 6, 2017 at 3:37 PM, Charles R Harris <charlesr.har...@gmail.com> wrote: > > > On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> Hi, >> >> On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris >> <charlesr.har...@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 >> > compiled >> > 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 >> > week. >> > At this point it looks like the best thing to do is release 1.13.1 >> > compiled >> > 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? >> >> Cheers, >> >> Matthew > > > Haste makes waste ;) I'd rather put off the move to OpenBlas to 1.14 to > allow more time for it to settle,
I'd only say that I don't know of any settling that is likely to happen. I suspect that not many people have tried the experimental wheels. I've automated the build process both for OpenBLAS and the OpenBLAS wheels, and I believe those are solid now. > and compiling against Python 3.6.0 seems > like more work than it is worth, Probably about two hours of futzing on Appveyor - your call - I'm happy not to do it :) Cheers, Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
