RetroSearch Browse

Fri May 4 14:55:35 EDT 2018 · https://mail.python.org/pipermail/python-dev/2018-May/153397.html

On Fri, May 4, 2018, 11:50 Serhiy Storchaka <storchaka at gmail.com> wrote:

>
> Ideally any deprecated feature should have a replacement, and this
> replacement should be available in at least one version before adding
> the deprecation warning.
>
> X.Y: added a replacement
>
> X.Y+1: added a deprecation warning. Many users need to support only two
> recent versions and can move to using the replacement now.
>

Isn't the whole point of making DeprecationWarnings hidden by default that
it lets us add the new thing and deprecate the old thing in the same
release, without creating too much disruption?

-n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180504/4caf7fb3/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2018-May/153397.html below:

[Python-Dev] Process to remove a Python feature