Fair enough, I don't necessarily disagree with you. Would removing the documentation for ifequal be OK? At least that would prevent new projects from using it or being confused about multiple ways to compare values.
On Friday, 7 August 2015 12:49:37 UTC+10, Karen Tracey wrote: > > We certainly weren't discussing removing without deprecating, were we? I'm > saying removing isn't worth the hassle to users, period. My opinion from > working on a fair number of inherited sites, plus sites where I don't get > to choose who contributes code I'm responsible for maintaining. I've > reported I have code I have to maintain written last year that uses these > tags, it's not just ancient crufty old stuff. These tags don't cause a > massive "brain stop" to figure out what "ifequal" might mean when > encountering them in existing templates.They are not that bad. This wart > isn't worth the pain to users to remove, in my opinion. Finding and fixing > all templates used by a site is NOT trivial. Fixing url was worth it. This > is not. > > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/44ee5d1f-1071-4dd7-a1dd-fe798c0dc2de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
