[Numpy-discussion] NumPy 1.20.x branch in two weeks

[Mark Harfouche]

>
>
> Do you think the proposal is not in compliance? There is no requirement
> that we drop anything more than 42 months old, it is just recommended. The
> change in the Python release cycle has created some difficulty. With the
> yearly cycle, 4 python yearly releases will cover 3-4 years, which seems
> reasonable and we can probably drop to 3 releases towards the end, but with
> 3.7 coming 18 months after 3.6, four releases is on the long side, and
> three releases on the short side, so keeping 3.6 is the conservative
> choice. Once the yearly cycle sets in I think we will be fine.
>
> Chuck
>

I believe that it really helps to "lead by example".

I don't mean to reference threads that you have all participated in, but
the discussion in:
https://mail.python.org/pipermail/scipy-dev/2020-August/024336.html

Makes it clear to me at least, that downstream will follow the example that
numpy sets.

At the time of writing, it was anticipated that Python 3.7, 3.8, and maybe
3.9 would exist in Nov 1st.
The support table
https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table
suggests that any release July 23 should only support 3.7.

Barring COVID delays, it seems natural that in Nov 2020, support for Python
3.6 be dropped or that the NEP be revised.

These decisions are hard, and take up alot of mental capacity, if the
support window needs revisiting, that is fine, it just really helps to be
able to point to a document (which is what NEP29 seemed to do).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/numpy-discussion/attachments/20201101/83c4396d/attachment-0001.html>