policy on minimal python supported

[Reimundo Heluani]

Good morning, I see that support for Python 3.8.x is about to be merged in
#27754. I want to add a parallel computation ticket and I was wandering if I
could use multiprocessing.parent_process() which is only available starting
with 3.8. What's the minimal Python version that Sage has to accept, and more
importantly where do I track this?

Thanks,

R.

[Samuel Lelievre]

2020-08-30 10:05:46 UTC+2, Reimundo Heluani:

>

> I want to add a parallel computation ticket and I was

> wondering if I could use multiprocessing.parent_process()

> which is only available starting with 3.8.

It might be possible to provide some functionality

which only works if the current Python is >= 3.8,

and otherwise either falls back to non-parallel

or raises an error.

2020-08-30 10:05:46 UTC+2, Reimundo Heluani:

>

> What's the minimal Python version that Sage has to accept,

> and more importantly where do I track this?

Currently we aim to support Python 3.6 to 3.8.

Using Sage Trac's query engine to look for all tickets

with "python" in the ticket summary,

  https://trac.sagemath.org/query?order=id&desc=1&summary=~python

we can find some relevant tickets.

One of them especially is about adopting a clear policy

in that regard:

- Adopt the “time window-based” policy

  for support of Python versions from NEP 29

  https://trac.sagemath.org/ticket/30384

See also:

- Support minimal system Python version 3.6 (for venv)

  https://trac.sagemath.org/ticket/29033

  merged in Sage 9.2.beta2, as you can find out

  by visiting sage-release and putting the ticket number,

  here 29033, in the search field.

More tips for finding out in which commit or in which

version some change happened were recently discussed

on sage-devel:

  https://groups.google.com/d/topic/sage-devel/7pq6iJH45KU/discussion

Support for Python 3.9 is discussed at:

- Support Python 3.9

  https://trac.sagemath.org/ticket/30184

[Reimundo Heluani]

On August 30, 2020 9:25:39 AM GMT-03:00, Samuel Lelievre <samuel....@gmail.com> wrote:
>2020-08-30 10:05:46 UTC+2, Reimundo Heluani:
>>
>> I want to add a parallel computation ticket and I was
>> wondering if I could use multiprocessing.parent_process()
>> which is only available starting with 3.8.
>
>It might be possible to provide some functionality
>which only works if the current Python is >= 3.8,
>and otherwise either falls back to non-parallel
>or raises an error.
>
>
>2020-08-30 10:05:46 UTC+2, Reimundo Heluani:
>>
>> What's the minimal Python version that Sage has to accept,
>> and more importantly where do I track this?
>
>Currently we aim to support Python 3.6 to 3.8.
>
>Using Sage Trac's query engine to look for all tickets
>with "python" in the ticket summary,
>
> https://trac.sagemath.org/query?order=id&desc=1&summary=~python
>
>we can find some relevant tickets.
>
>One of them especially is about adopting a clear policy
>in that regard:
>
>- Adopt the “time window-based” policy
> for support of Python versions from NEP 29
> https://trac.sagemath.org/ticket/30384
>

Thanks that's exactly what I needed.

R

>See also:
>
>- Support minimal system Python version 3.6 (for venv)
> https://trac.sagemath.org/ticket/29033
>
> merged in Sage 9.2.beta2, as you can find out
> by visiting sage-release and putting the ticket number,
> here 29033, in the search field.
>
>More tips for finding out in which commit or in which
>version some change happened were recently discussed
>on sage-devel:
>
> https://groups.google.com/d/topic/sage-devel/7pq6iJH45KU/discussion
>
>Support for Python 3.9 is discussed at:
>
>- Support Python 3.9
> https://trac.sagemath.org/ticket/30184

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Michael Orlitzky]

This came up recently at

https://groups.google.com/forum/#!msg/sage-devel/fgsSsJmVVXo/ZIcJq9x3AAAJ