[Python-Dev] Removing PendingDeprecationWarning (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sun Mar 24 07:57:46 EDT 2019
- Previous message (by thread): [Python-Dev] Removing PendingDeprecationWarning
- Next message (by thread): [Python-Dev] Removing PendingDeprecationWarning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 22 Mar 2019 at 12:45, Inada Naoki <songofacandy at gmail.com> wrote:
Hi, all. I'm thinking about removing PendingDeprecationWarning. (previous discussion: https://discuss.python.org/t/pendingdeprecationwarning-is-really-useful/1038) It was added "not be printed by default" version of DeprecationWarning. But DeprecationWarning is not printed by default now.
No, this was covered in PEP 565, and PendingDeprecationWarning was explicitly kept as a way of opting out of the revised semantics of DeprecationWarning.
In Python 3.7 and above, the semantics are:
- PendingDeprecationWarning: never shown by default
- DeprecationWarning: shown by default in the main module
- FutureWarning: shown by default everywhere
PEP section: https://www.python.org/dev/peps/pep-0565/#additional-use-case-for-futurewarning
The documentation was also updated to match:
- https://docs.python.org/3/library/warnings.html#warning-categories
- https://docs.python.org/3/library/exceptions.html#warnings
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Removing PendingDeprecationWarning
- Next message (by thread): [Python-Dev] Removing PendingDeprecationWarning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]