Nick Coghlan ncoghlan at gmail.com
Mon Mar 25 07:53:07 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 Mon, 25 Mar 2019 at 14:39, Inada Naoki <songofacandy at gmail.com> wrote:
> We have many ways to deprecation:
>
> * Document only deprecation (no warning) -- no actual removal is planned.
> * FutureWarning -- to warn end users.
> * DeprecationWarning -- to warn Python developers.
> * PendingDeprecationWarning -- to warn Python developers.

The key difference between the last two:

* DeprecationWarning: the decision has already been made, you have
little chance of getting the deprecation reversed
* PendingDeprecationWarning: full deprecation is being considered, now
is the time to get in touch if you'd like to avoid full deprecation

Hence the last one only showing up to those folks that are running
automated tests or otherwise enabling all 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 ]

---

More information about the Python-Dev mailing list