[Python-Dev] Removing PendingDeprecationWarning (original) (raw)

Inada Naoki songofacandy at gmail.com
Fri Mar 22 04:16:08 EDT 2019

On Fri, Mar 22, 2019 at 5:06 PM Victor Stinner <vstinner at redhat.com> wrote:

Le ven. 22 mars 2019 à 08:54, Inada Naoki <songofacandy at gmail.com> a écrit : > Yes. It will be removed at some point, but not in near future. > > But when when backward compatibility can be kept by alias, > we can be very lazy about removing it. Honestly, I don't see the point of removing PendingDeprecationWarning anytime soon. Practicality beats purity.

I totally agree.

Removing PendingDeprecationWarning doesn't bring any value to anyone. "PendingDeprecationWarning = DeprecationWarning" costs nothing in term of maintenance.

If you care, I would suggest to invest time in static analyzers like pycodestyle, pylint, pyflakes, etc. Emit a warning with a low priority, and let users make their own choices.

Agree too.

> We have socket.error for long time. And it's perfectly fine, no?

Yes. Waiting 10+ years to remove aliases is fine.

-- Inada Naoki <songofacandy at gmail.com>

More information about the Python-Dev mailing list