On Thu, 2010-10-07 at 11:30 +0800, Russell Keith-Magee wrote: > Strictly, it needs to be put on a deprecation path, because it *is* > documented, in ref/settings.txt. So the earliest we can truly remove > it is in 1.5, after a PendingDeprecationWarning in 1.3 and a full > Warning in 1.4. > > Along the way, we should also be removing COMMENTS_ALLOW_PROFANITIES, > since there isn't much point having one without t'other.
Although we cannot remove it in 1.3, could we set the default value to an empty list? I imagine that people who are depending on its functionality will have set their own value in their settings.py, and they can easily do so if they haven't already. Luke -- "Dysfunction: The only consistent feature of all of your dissatisfying relationships is you." (despair.com) Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
