On Tue, Oct 4, 2011 at 9:40 AM, Joe & Anne Tennies <tenn...@gmail.com> wrote: > I know that no one knows who I am, but I'm going to say that this is > becoming a bike shed.
There appears to be some confusion here -- nobody is proposing changing *anything* about Django's deprecation policy. All we are doing is attempting to get some consistency in the *language* that we use, especially in the deprecation guide document [1]. If you read the current document, the language used varies wildly -- see Luke's original email for a full list of the problems). In the interests of clarity, Luke has proposed normalizing the language, and so far, I haven't seen any disagreement that the language cleanup he has proposed is the right thing to do. All I've noted is that there is an unfortunate inconsistency in the naming of PendingDeprecation, but there's not much we can do about that. [1] https://docs.djangoproject.com/en/dev/internals/deprecation/ Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
