On Fri, May 4, 2018, 11:50 Serhiy Storchaka <storch...@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
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
