
On Fri, 24 Jan 2020 at 14:46, Ethan Furman <ethan@stoneleaf.us> wrote:
On 01/23/2020 03:36 PM, Barry Warsaw wrote:
On Jan 23, 2020, at 14:03, Victor Stinner wrote:
It's not only about specific changes, but more a discussion about a general policy to decide if a deprecated feature should stay until 3.10, or if it's ok to remove it in 3.9.
Given that we’ve changed the release cadence to one major release per year, it doesn’t seem that much of a burden to revert and carry these changes forward into Python 3.10. And if it helps with the migration off of Python 2.7, then +1 from me.
I suspect anyone who's waited this long to switch to Python 3 will be okay with staying on 3.8 for a few years.
The issue isn't end users, it is projects who will then be incompatible with 3.10 for "a few years." -Rob