[Python-Dev] Removing PendingDeprecationWarning

Brett Cannon brett at python.org
Wed Mar 27 12:58:21 EDT 2019


On Wed, Mar 27, 2019 at 3:26 AM Inada Naoki <songofacandy at gmail.com> wrote:

> On Mon, Mar 25, 2019 at 10:11 PM Inada Naoki <songofacandy at gmail.com>
> wrote:
> >
> > C, Rust, Java, Ruby, PHP, don't have PendingDeprecation.
> > Programmers only need Deprecation.  Why programmers need
> PendingDeprecation
> > only in Python?
> >
>
> Any comments about this?
>

You know my views on this. :) Leave it and we start to consistently use if
for deprecations that are more than a release away from removal (and for
those not reading discuss.python.org, I proposed over there introducing a
warnings._deprecate() function for the stdlib which will do the right thing
based on sys.version_info() and the stated start/end for the deprecation).

It might also make sense to hold off on anything official until we decide
on something like PEP 387 and how we want to officially communicate
deprecations.

-Brett


>
> I want to document PendingDeprecationWarning is deprecated [1].
> May I merge the PR?  Should I start poll on discuss.python.org?
>
> [1]: https://github.com/python/cpython/pull/12505/files
>
> --
> Inada Naoki  <songofacandy at gmail.com>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190327/32bbf300/attachment.html>


More information about the Python-Dev mailing list