On Tue, May 11, 2021 at 12:12 AM 'Travis Scrimshaw' via sage-devel
<sage-devel@googlegroups.com> wrote:
>
> On #30423, which is getting close to completion, we will be using 
> multiprocessing.shared_memory, which is only available on Python 3.8+. 
> However, right now we are at least allowing Python 3.7 (as per the patchbot). 
> So my main proposal would be to bump the minimum required Python version to 
> 3.8, which was released Oct. 14, 2019.
>
> On that ticket, we can make it so that the main entry point runs things in 
> serial if the Python version is sufficiently small and that the doc builds, 
> but the doctests for the parallel code will fail. So the first alternative 
> option would be to mark certain doctests (or the file) as needing a large 
> Python version.

As 3.7 still has 2 years to go before EOL, we'd rather keep it - I'd
just say tag the doctests with bigger versions of Python if needed.


>
> A second alternative is that this can be split off as a separate package 
> (either an optional Sage package or pip installable). Yet, it is somewhat 
> tightly coupled with the FusionRing code (and root systems) in Sage, so this 
> is not so desirable. A less invasive way would be to just split the parallel 
> part off, but this would take some work to do I think.
>
> What do people think?
>
> Best,
> Travis
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/e9bd34ce-3fac-4737-a8f8-a5203f2fd87en%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1EvH2DCh_th-Pki_f%3DDgAhE0h6%2BNhvb8Uo9UGww20gnA%40mail.gmail.com.

Reply via email to