On Fri, Oct 18, 2019 at 3:06 AM Ralf Gommers <ralf.gomm...@gmail.com> wrote:
> > > On Fri, Oct 11, 2019 at 4:18 AM Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Thu, Oct 10, 2019 at 6:02 PM Stefan van der Walt <stef...@berkeley.edu> >> wrote: >> >>> On Thu, Oct 10, 2019, at 09:34, Charles R Harris wrote: >>> >>> I think we can support 3.5 as long as we please, the question is how >>> long we *want* to support it. I don't plan to release 1.18 wheels for 3.5, >>> but I'm concerned about making 1.18 outright incompatible with 3.5. I would >>> like to see the random interface settle before we do that. So my preference >>> would be to drop 3.5 in 1.19 with a future warning in the 1.18 release >>> notes. Alternatively, we could backport all the random changes to 1.17, but >>> I would rather not do that. >>> >>> > I'm not sure I like this approach, which is reflected in the current > version of https://github.com/numpy/numpy/pull/14673. If we stop testing > 3.5 in CI, don't release 3.5 wheels and remove the PyPI trove classifier > for it (so installation tools may not install it anymore), then what's the > point of saying we "don't drop it"? I'd rather keep it fully supported for > one more month and release a couple of wheels, or just drop it completely. > I don't have much of a preference which option is better, just would like > to avoid half-dropping it. > > That's fair. The 1.17.3 release supporting Python 3.5--3.8 went well enough. The only glitch was that I had to explicitly use OSX 10.6 and icode 6.4 for the 3.5 wheels on the Mac. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
