On Thu, Jul 6, 2017 at 6:10 AM, Charles R Harris <charlesr.har...@gmail.com> wrote:
> I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up > fixing #29943 <https://bugs.python.org/issue29943> so we can close #9272 > <https://github.com/numpy/numpy/issues/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. > If it's compiled against 3.6.0 will it work fine with 3.6.1? and probably 3.6.2 as well? If so, it would be nice to do it that way, if Matthew doesn't mind :-) But either way, it'll be good to get it out. Thanks! -CHB > 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. > > Thoughts? > > Chuck > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
