[Python-Dev] Process to remove a Python feature (original) (raw)
Guido van Rossum guido at python.org
Fri May 4 14:59:25 EDT 2018
- Previous message (by thread): [Python-Dev] Process to remove a Python feature
- Next message (by thread): [Python-Dev] Process to remove a Python feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
No, the reason they're hidden by default is that for most users they're not actionable most of the time.
On Fri, May 4, 2018 at 11:55 AM, Nathaniel Smith <njs at pobox.com> wrote:
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
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ guido%40python.org
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180504/1be8e1e4/attachment.html>
- Previous message (by thread): [Python-Dev] Process to remove a Python feature
- Next message (by thread): [Python-Dev] Process to remove a Python feature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]