On Wednesday, June 5, 2024 at 12:37:38 PM UTC-7 Oscar Benjamin wrote: On Wed, 5 Jun 2024 at 19:32, Matthias Koeppe <matthia...@gmail.com> wrote: > On Wednesday, June 5, 2024 at 5:31:30 AM UTC-7 Oscar Benjamin wrote: > > Following those specifications in coordination with other scientific > > Python packages would mean dropping both 3.8 and 3.9 now and then also > > dropping 3.10 in a few months. I don't propose to do this right now > > with the SymPy 1.13 release but once 1.13 is released I want to drop > > at least 3.8 if not also 3.9 > > No problem; by the time that SymPy 1.14 is ready, we'll likely have dropped 3.9.
Okay great. We'll drop both Python 3.8 and 3.9 then after sympy 1.13 is released. You haven't mentioned 3.10. I infer from this that it currently seems problematic for Sage to drop support for 3.10 in a few months (and that it might be awkward if SymPy did so). Sorry for missing your question regarding 3.10. That's really where it becomes relevant what "following the SPEC 0/NEP 29 schedule" really means for a project. (I have a bit of analysis on the actual practices of projects in our wiki page; it varies quite a bit, and more variation comes in simply from the coarse granularity of release schedules.) If you drop Python 3.10 in preparation for a SymPy 1.14 release at the end of 2024, I think that you are likely going to be early in the pack with this, and in Sage we might be holding off on the update for a while -- unless there's a SymPy feature that is of particular importance for us, or we notice that Python 3.10 does not matter regarding system Python support on distributions, or NumPy/SciPy releases that drop the support are ready also, etc. Matthias -- 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/9a3cd9c6-978f-4acf-bd8d-c15c0c6b7e71n%40googlegroups.com.
