On Sun, Nov 5, 2017 at 10:25 AM, Charles R Harris <charlesr.har...@gmail.com > wrote:
> the timeline I've been playing with is to keep Python 2.7 support through > 2018, which given our current pace, would be for NumPy 1.15 and 1.16. After > that 1.16 would become a long term support release with backports of > critical bug fixes > +1 I think py2.7 is going to be around for a long time yet -- which means we really do want to keep the long term support -- which may be quite some time. But that's doesn't mean people insisting on no upgrading PYthon need to get the latest and greatest numpy. Also -- if py2.7 continues to see the use I expect it will well past when pyton.org officially drops it, I wouldn't be surprised if a Python2.7 Windows build based on a newer compiler would come along -- perhaps by Anaconda or conda-forge, or ??? If that happens, I suppose we could re-visit 2.7 support. Though it sure would be nice to clean up the dang Unicode stuff for good, too! In short, if it makes it easier for numpy to move forward, let's do it! -CHB -- 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
