I'd like to stress one important point already made : dropping support for old/antique/paleontologic versions of Python lightens the maintainance workload of the *small* team of Sage developpers.
Given the size and the state of this team, this point should *not* be taken lightly... I'd also like to hear on this point from our release manager : would this proposed policy change have an influence on his workload ? HTH, Le vendredi 26 mai 2023 à 20:54:22 UTC+2, Michael Orlitzky a écrit : > On Fri, 2023-05-26 at 18:15 +0100, Oscar Benjamin wrote: > > > > What is wrong with Sage just saying that an older version of an > > operating system only works with an older version of Sage? > > Matthias alluded to this when he mentioned that we only have one > release branch of sage. Our version numbers are not really meaningful, > and bug fixes and features are released simultaneously. So the only way > to get fixes for critical bugs is to upgrade, but the upgrades come > with new features, and those new features can have new requirements. > > That said, I still share your sentiment when there is a good reason (a > term best left undefined) to break compatibility. > > -- 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/3fa0c337-22e0-45eb-8baa-8a52dacaec7cn%40googlegroups.com.
