On Fri, Aug 7, 2015 at 3:06 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> > On 7 août 2015, at 05:43, Curtis Maloney <cur...@acommoncreative.com>
> wrote:
> >
> > I'd probably go with updating the documentation to say they're legacy
> > tags, you're better off using {% if %} now, and warn they may be
> > removed in a later release.
>
> This is my inclination as well. Then we can revisit the topic in a few
> years :-)
>
> I agree. We shouldn't encourage new users to use the {% ifequal %} tag,
but I don't see any benefit in removing something that is in use, and
doesn't pose any particular maintenance burden or impediment to progress.
The only other suggestion I've got is to add a new "pre-deprecation" step
to our deprecation process - a flag that lets us indicate that at some
point, we intend to deprecate something, but we haven't decided when that
will be. This would essentially be a "don't use this on new code, but
there's no rush in replacing it". It could also be accompanied with a
Warning so that existing uses could be found and replaced if someone was so
inclined.
Yours,
Russ Magee %-)
--
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/CAJxq848UjiMPG%2B6WwzcHUBnZQbhFqXtKGWa8Uq3PxctHuy60xg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
