Christopher Barker writes: > On Sun, Nov 14, 2021 at 8:19 AM Stephen J. Turnbull < > stephenjturnb...@gmail.com> wrote: > > > > But do > > > we need to support running the same code on 3.5 to 3.10? > > > > Need? No. Want to not raise a big middle finger to our users? > > Note that I said 3.5, not 3.6 -- 3.5 is no longer supported. If we feel the > need to be backward compatible with unsupported versions that we can't ever > remove anything.
I'm not saying *Python* can't remove anything. I'm saying downstream, *GNU Mailman* has users it *may* want to support. Unlike Petr, I'm not <0 on removals. But they are costly, keeping up with deprecations is costly. In theory, I agree with you that we should consider maintenance as an almost-fixed cost that a few deprecations aren't going to increase significantly. In practice, I'm not practiced enough to say. I do see a strong case for pruning stuff that we already found worth deprecation as well. In this thread, I'm most interested in exploring tooling to make it easier for those who express reservations about removals. Steve _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/5YTXKZQT4IQSZDLFGT4TRFHIOYHCYITU/ Code of Conduct: http://python.org/psf/codeofconduct/
