On 03/02/2020 22:06, Mike Miller wrote:
On 2020-02-03 01:50, Petr Viktorin wrote:
When the changes are rolled out gradually across minor releases, those
that cause unforeseen trouble in real-world code can be identified in
the alphas/betas, and rethought/reverted if necessary.
To be clear, my suggestion was to maintain gradual deprecations and
warnings, but have a single removal event at the start of a new version
major number. So there will be many years of betas and releases to
haggle over.
I think that just enables laziness. "We don't need to worry about the
deprecations, nothing is going to happen for years yet," is more or less
what happened with the Python2 to Python3 shift. People naturally enjoy
adding shiny new features to their projects over maintenance.
As a refinement to the idea above, perhaps a sub rule could be added:
- No deprecations should appear in a X.9 release to give folks time
to prepare.
That feels like a very bad idea indeed. If you don't tell people things
are going away, they definitely won't prepare for that.
--
Rhodri James *-* Kynesim Ltd
_______________________________________________
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/43S4KEWSIYTZ7HBZ6KBYEMFZG6KUQOBD/
Code of Conduct: http://python.org/psf/codeofconduct/
