On 01/23/2020 07:02 PM, Robert Collins wrote:
On Fri, 24 Jan 2020 at 14:46, Ethan Furman <ethan@stoneleaf.us <mailto: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."
I'm sure you meant 3.9, since 3.10 would still have the removals. My understanding is that this postponement of removals is aimed at those who have just migrated to Python 3, not those who have already done it nor those who have 2/3 straddling code bases. For those who have been on 3 for a while, updating to use the newer APIs for 3.9 vs 3.10 shouldn't make a difference. Like-wise for those with 2/3 straddling code bases (we'll just need to add a few more things to our shims). Anyone who hasn't supported/used Python 3 until now shouldn't have a problem with sticking with 3.8 until they are ready to make more adjustments, and those who have had to keep Python 2 around to run those applications/frameworks/whatevers will, I should think, be thrilled to use any Python 3 instead. :-) -- ~Ethan~