[SciPy-Dev] Minimum Python the codebase needs to support

[Ralf Gommers]

On Tue, Jan 14, 2020 at 11:37 AM Evgeni Burovski <evgeny.burovskiy at gmail.com>
wrote:

> How about continuing the cadence we had for 2.7 --- drop the CI in 1.3,
> but postpone code removals until 1.5?
>
> This can be year based (two minor releases, one full year) or release
> based (one minor release, 1/2 year).
>

That sounds reasonable to me. In master Python 3.5 is already dropped, so
for new code we can start using 3.6+ features. But there's no reason to
start cleaning up straight away and perhaps make backports harder.

Ralf


> Evgeni
>
> вт, 14 янв. 2020 г., 13:17 Kai Striega <kaistriega at gmail.com>:
>
>> The minimum for SciPy 1.4 (Dec '19) is 3.5.
>>
>> Saying that, the toolchain roadmap [1] list the target for 2020 to be 3.6.
>>
>> [1]_https://docs.scipy.org/doc/scipy/reference/toolchain.html
>>
>> On Tue, 14 Jan 2020 at 18:06, Andrew Nelson <andyfaff at gmail.com> wrote:
>>
>>> What is the minimum Python version the codebase needs to support? There
>>> are plenty of cleanups possible as the minimum version increases. From PyPI
>>> it looks like we still need to cope with 3.5?
>>> _______________________________________________
>>> SciPy-Dev mailing list
>>> SciPy-Dev at python.org
>>> https://mail.python.org/mailman/listinfo/scipy-dev
>>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20200114/3a76ca70/attachment.html>