solipsis at pitrou.net
Fri Mar 23 12:12:05 CET 2012
On Thu, 22 Mar 2012 17:13:27 -0400
Terry Reedy <tjreedy at udel.edu> wrote:
> My impression is that the original reason for PendingDeprecationWarning
> versus DeprecationWarning was to be off by default until the last
> release before removal. But having DeprecationWarnings on by default was
> found to be too obnoxious and it too is off by default. So do we still
> need PendingDeprecationWarnings? My impression is that it is mostly not
> used, as it is a nuisance to remember to change from one to the other.
> The deprecation message can always indicate the planned removal time. I
> searched the Developer's Guide for both deprecation and
> DeprecationWarning and found nothing.
Warnings are not only for us, they are for third-party libraries.
In this case it seems removing PendingDeprecationWarning would be a
More information about the Python-Dev