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

Showing content from https://mail.python.org/pipermail/python-dev/2019-March/156806.html below:

[Python-Dev] Removing PendingDeprecationWarning

• Previous message (by thread): [Python-Dev] Best way to specify docstrings for member objects
• Next message (by thread): [Python-Dev] Removing PendingDeprecationWarning
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

We use PendingDeprecationWarning for N-2 release, and change it to
DeprecationWarning for N-1 release.  But this workflow seems not worth
enough for now.

I want to stop using PendingDeprecationWarning for new deprecation.

More aggressively, I want to remove PendingDeprecationWarning class,
and `PendingDeprecationWarning = DeprecationWarning` for backward
compatibility.

How do you think?  May I do it in Python 3.8?

-- 
Inada Naoki  <songofacandy at gmail.com>

• Previous message (by thread): [Python-Dev] Best way to specify docstrings for member objects
• Next message (by thread): [Python-Dev] Removing PendingDeprecationWarning
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4