On Fri, Mar 22, 2019 at 7:36 PM Serhiy Storchaka <storch...@gmail.com> wrote: > > > > > How do you think? May I do it in Python 3.8? > > What is wrong with PendingDeprecationWarning? What problem do you want > to solve at the cost of removing this feature? >
The main problem is complexity. In other words, learning cost. All Python library developer would like to know how to deprecate something. They will understand "deprecated" means "will be removed in the future version" easily. Then, "will be deprecated" [1] is easy to understand? "will be (will be removed)" is very curious. To understand what PendingDeprecationWarning is for, they need to learn history which is not documented in clearly. [1]: https://docs.python.org/3/library/exceptions.html#PendingDeprecationWarning If we deprecate PendingDeprecationWarning, people don't have to understand what it is for. > Now, when DeprecationWarning is displayed by default in the interactive > session, in __main__ and in development runtime mode (and this list can > be extended), PendingDeprecationWarning is useful again. Even if the > interpreter itself would not use it, it is used in third-party projects. > This benefits seems too small compared to the learning cost. -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ 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
