I also feel the NEP is very useful since it helps downstream to drop older versions relatively early. I’ve found this very useful in projects that have less maintenance bandwidth. Kevin From: Jarrod Millman I also misunderstood the purpose of the NEP. I assumed it was intended to encourage projects to drop old versions of Python. Other people have viewed the NEP similarly: https://github.com/networkx/networkx/issues/4027 If the intention of the NEP is to specify that projects not drop old version of Python too early, I don't think it is obvious from the NEP. It would be helpful if you added a simple motivation statement near the top of the document. Something like: ## Motivation and Scope The purpose of the NEP is to ensure projects in the scientific Python ecosystem don't drop support for old version of Python and NumPy too soon. On Sun, Nov 1, 2020 at 6:44 PM Jarrod Millman <mill...@berkeley.edu> wrote: > > NetworkX is currently planning to support 3.6 for our coming 2.6 > release (dec 2020) and 3.0 release (early 2021). We had originally > thought about following NEP 29. But I assumed it had been abandoned, > since neither NumPy nor SciPy dropped Python 3.6 on Jun 23, 2020. > > NetworkX is likely to continue supporting whatever versions of Python > both NumPy and SciPy support regardless of what NEP 29 says. I > wouldn't be surprised if other projects do the same thing. > > Jarrod _______________________________________________ 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
