# PendingDeprecationWarning is really useful?

**URL:** <https://discuss.python.org/t/pendingdeprecationwarning-is-really-useful/1038>\
**Category:** Ideas\
**Created:** [March 19, 2019, 8:16am UTC](https://discuss.python.org/t/pendingdeprecationwarning-is-really-useful/1038 "2019-03-19T08:16:04Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [March 20, 2019, 6:26pm UTC](https://discuss.python.org/t/pendingdeprecationwarning-is-really-useful/1038/10 "2019-03-20T18:26:02Z")

</div>

> [@Senthil](#):
>
> This is my observation too. We have not been rigorous about deprecating things which have expressed DeprecationWarning for.

I think part of that is because we have not been removing anything due to Python 2 compatibility. But yes, we have not been great at this.

> [@Senthil](#):
>
> PendingDeprecationWarning may be worser, as the developer will have to track to deprecate it after the N releases in future.

I’ve contemplated adding something to `warnings` where you specify what version of Python something is scheduled to be removed in and then it would raise `PendingDeprecationWarning` in \>N version, `DeprecationWarning` in N, and raise a `RuntimeError` or something for N+1 so it doesn’t get forgotten.

---

_[View the full topic](https://discuss.python.org/t/pendingdeprecationwarning-is-really-useful/1038)._