RetroSearch Browse

Fri Mar 22 03:53:50 EDT 2019 · https://mail.python.org/pipermail/python-dev/2019-March/156810.html

On Fri, Mar 22, 2019 at 4:40 PM Victor Stinner <vstinner at redhat.com> wrote:
>
>
> > More aggressively, I want to remove PendingDeprecationWarning class,
> > and `PendingDeprecationWarning = DeprecationWarning` for backward
> > compatibility.
>
> I'm not sure that I understand well. Do you want to remove the
> PendingDeprecationWarning builtin symbol, or just make it an alias to
> DeprecationWarning.
>
> I'm fine with "PendingDeprecationWarning = DeprecationWarning".
>

I meant an alias in builtin.

> IMHO your email title is misleading. You don't want to *remove*
> PendingDeprecationWarning, you only want to make it an alias to
> DeprecationWarning, right? In term of backward compatibility, it's
> very different :-)
>
> Victor

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.

We have `socket.error` for long time.

Regards,
-- 
Inada Naoki  <songofacandy at gmail.com>

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

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

[Python-Dev] Removing PendingDeprecationWarning