Message195824
| 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". |
|