Accepting NEP 29 — Recommend Python and Numpy version support as a community policy standard
Hi all, we propose formally accepting the NumPy enhancement proposal 29: "Recommend Python and Numpy version support as a community policy standard" available at: https://numpy.org/neps/nep-0029-deprecation_policy.html If there are no objections within a week it may be accepted. This proposal is a recommendation to the larger ecosystem and thus should receive attention and acceptance from a wide audience. However, lets try to keep discussions on the NumPy mailing list. The most important points from the Abstract and Implementation sections are: "This NEP recommends that all projects across the Scientific Python ecosystem adopt a common “time window-based” policy for support of Python and NumPy versions. Standardizing a recommendation for project support of minimum Python and NumPy versions will improve downstream project planning. …" and: "We suggest that all projects adopt the following language into their development guidelines: This project supports: * All minor versions of Python released 42 months prior to the project, and at minimum the two latest minor versions. * All minor versions of numpy released in the 24 months prior to the project, and at minimum the last thee minor versions." For the full text, please refer to the link above. Cheers, Sebastian
We're behind this at scikit-image! Thank you to all who worked on this proposal! Minor typo: "at minimum the last THREE minor versions" Juan. On Thu, 3 Oct 2019, at 4:54 PM, Sebastian Berg wrote:
Hi all,
we propose formally accepting the NumPy enhancement proposal 29:
"Recommend Python and Numpy version support as a community policy standard"
available at: https://numpy.org/neps/nep-0029-deprecation_policy.html
If there are no objections within a week it may be accepted. This proposal is a recommendation to the larger ecosystem and thus should receive attention and acceptance from a wide audience. However, lets try to keep discussions on the NumPy mailing list.
The most important points from the Abstract and Implementation sections are:
"This NEP recommends that all projects across the Scientific Python ecosystem adopt a common “time window-based” policy for support of Python and NumPy versions. Standardizing a recommendation for project support of minimum Python and NumPy versions will improve downstream project planning. …"
and:
"We suggest that all projects adopt the following language into their development guidelines:
This project supports: * All minor versions of Python released 42 months prior to the project, and at minimum the two latest minor versions. * All minor versions of numpy released in the 24 months prior to the project, and at minimum the last thee minor versions."
For the full text, please refer to the link above.
Cheers,
Sebastian
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
*Attachments:* * signature.asc
participants (2)
-
Juan Nunez-Iglesias
-
Sebastian Berg