[Numpy-discussion] Proposal of timeline for dropping Python 2.7 support
ilhanpolat at gmail.com
Wed Nov 8 12:15:39 EST 2017
I was about to send the same thing. I think this matter became a vim/emacs
issue and Py2 supporters won't take any arguments anymore. But if Instagram
can do it, it means that legacy code argument is a matter of will but not a
Also people are really going out of their ways such as Tauthon
https://github.com/naftaliharris/tauthon to stay with Python2. To be
honest, I'm convinced that this is a sentimental debate after seeing this
On Wed, Nov 8, 2017 at 5:50 PM, Peter Cock <p.j.a.cock at googlemail.com>
> On Tue, Nov 7, 2017 at 11:40 PM, Nathaniel Smith <njs at pobox.com> wrote:
> > <snip>
> > Right now, the decision in front of us is what to tell people who ask
> > numpy's py2 support plans, so that they can make their own plans. Given
> > we know right now, I don't think we should promise to keep support past
> > 2018. If we get there and the situation's changed, and there's both
> > and means to extend support we can revisit that. But's better to
> > under-promise and possibly over-deliver, instead of promising to support
> > until after it becomes a millstone around our necks and then realizing we
> > haven't warned anyone and are stuck supporting it another year beyond
> > that...
> > -n
> NumPy (and to a lesser extent SciPy) is in a tough position being at the
> bottom of many scientific Python programming stacks. Whenever you
> drop Python 2 support is going to upset someone.
> It is too ambitious to pledge to drop support for Python 2.7 no later than
> 2020, coinciding with the Python development team’s timeline for dropping
> support for Python 2.7?
> If that looks doable, NumPy could sign up to http://www.python3statement.
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion