On Oct 1, 9:10 am, Luke Plant <l.plant...@cantab.net> wrote: > Hi all, > > The Django deprecation timeline [1] is very inconsistent in its usage of > the terminology 'deprecated'. For example, the 1.5 section often says > "is deprecated" or "has been deprecated", when what they mean is "will > be removed", which is what the other sections generally tend to say. > Some in section 1.6 say a feature "will be deprecated".
I'm +1 on this, it essentially inconsistently restates the deprecation policy for each item. Not all deprecations are removals, some are API changes. I still think that the doc is basically forward looking, so future tense should be preserved - I don't think any mention of when the item was first deprecated is needed (as I said, that is in the policy and does not need to be repeated). I do think links to sections of release notes are useful instead of restating the reasons in full. On Oct 3, 6:35 am, Russell Keith-Magee <russ...@keith-magee.com> wrote: > +1. I agree with Paul that "PendingDeprecationWarning" is slightly > problematic from a language perspective because we're saying that > we're deprecating a feature now, and implementing that by raising a > Pending warning. However, I think that's a mild inconsistency I can > live with. regarding PendingDeprecationWarning: given that the policy is a relatively generous 2 version path, I like that PendingDeprecationWarning allows a sort of "soft deprecation". That is, if there was a large change in opinion (low probability), the deprecation could be reverted. Other's may object to this, but I think adopting sort of a deprecation "beta" would allow for some slightly more aggressive deprecation, with a period for community feedback. Many people will read release notes who don't pay attention to deprecation discussions in dev. The big downside to formalizing this is that the decision could appear wishy-washy, or could be subject to vocal minority crusades against a deprecation, so I'm +0 about it ;-) -Preston -- 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.
