➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients alex, barry, docs@python, eric.snow, ethan.furman, mark.dickinson, ncoghlan, serhiy.storchaka, vstinner
Date 2013-08-21.21:32:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7dHVRrLSJT_LRhhksHgG8W9dJbKvRn9BNchzashHnGkMQ@mail.gmail.com>
In-reply-to <1377064054.88.0.645596281376.issue17576@psf.upfronthosting.co.za>
Content 
On 21 Aug 2013 15:47, "Mark Dickinson" <report@bugs.python.org> wrote:
>
>
> Mark Dickinson added the comment:
>
> > Shouldn't it be PendingDeprecationWarning?
>
> Hmm.  Possibly.  I'm not sure what the policy is any more regarding
DeprecationWarning versus PendingDeprecationWarning.  Nick?

Not sure if this is written down anywhere, but I use
PendingDeprecationWarning for "definitely still around next release, may
not have a set date for removal" and DeprecationWarning for "may be removed
next release".
History
Date User Action Args
2013-08-21 21:32:15ncoghlansetrecipients: + ncoghlan, barry, mark.dickinson, vstinner, alex, docs@python, ethan.furman, eric.snow, serhiy.storchaka
2013-08-21 21:32:15ncoghlanlinkissue17576 messages
2013-08-21 21:32:15ncoghlancreate