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

[Mark Harfouche]

I know it seems silly, but would an amendment to NEP29 be reasonable?

Many downstream packages look to numpy to understand what versions should
be supported and NEP29 gave some good guidance.
That said, if it is worth ignoring, or revisiting, some clarity on how to
apply NEP29 given recent development would be appreciated.

Best,

Mark

On Sat, Oct 31, 2020 at 8:24 AM Ralf Gommers <ralf.gommers at gmail.com> wrote:

>
>
> On Thu, Oct 29, 2020 at 2:25 PM Charles R Harris <
> charlesr.harris at gmail.com> wrote:
>
>> Hi All,
>>
>> Time to start planning for the 1.20.x branch. These are my thoughts at
>> the moment:
>>
>>    - Keep support for Python 3.6. Python 3.7 came out in June 2018,
>>    which seems too recent to be our oldest supported version.
>>    - Drop Python 3.6 for 1.21.x, that will make the oldest supported
>>    version about three years old.
>>    - Drop manylinux1 for 1.21.x. It would be nice to drop earlier, but
>>    manylinux2010 is pretty recent.
>>
>> There were 33 wheels in the 1.19.3 release, I think we can live with that
>> for 1.20.x. I'm more worried about our tools aging out. After Python has
>> settled into its yearly release cycle, I think we will end up supporting
>> the latest 4 versions.
>>
>> Thoughts?
>>
>
> Seems reasonable to me.
>
> Cheers,
> Ralf
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/numpy-discussion/attachments/20201101/725a5680/attachment.html>