On Tuesday, 30 May 2023 at 11:13:27 UTC-7 tobia...@gmx.de wrote: that we normally drop support for older versions right after this support window (i.e. also adapt the drop schedule https://numpy.org/neps/nep-0029-deprecation_policy.html#drop-schedule). I've formulated an improved formulation for this policy at https://github.com/sagemath/sage/pull/35403#issuecomment-1566110884 which should hopefully clarify this point. (Dropping support means increasing `python_requires` and removing github tests for this old version, i.e. similar to https://github.com/sagemath/sage/pull/35404 which is modeled on the PR drooping Python 3.7.)
Formulated like this it would seem to me we could needlessly reduce the platforms that sage builds on: this suggests that the "drop Python 3.*" PR would get merged simply because it's time: in theory we could end up with a release where the sole commit is the dropping of support (in practice development is way too active for this). I would expect that such a PR would only get merged as a dependency of some other PR (that makes a fix, enhancement, or upgrades some other component). I guess another reason might be because we dropped testing on that Python version: once we're not testing we wouldn't know when it breaks and only reactively upping python_requires after someone reports a failure is probably not so nice. Having a policy that makes clear when such a drop PR is acceptable as a prerequisite for merging could save work and discussion. Numpy's schedule looks like a reasonable candidate for that. -- 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/fb01c984-560a-47cf-af3d-789cb1502342n%40googlegroups.com.
