It's also possible to work around the 3.6.1 problem with a small preprocessor hack. On my phone but there's a link in the bug report discussion.
On Jul 6, 2017 6:10 AM, "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 <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. 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 > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
