Hi all,
For the use case brought up originally, note
https://code.djangoproject.com/ticket/20684
In that spirit, I think the better solution for the more general case brought
here is a filter, say tag_attr, which takes a name and a value and renders them
appropriately:
{% for name, value in attrs.items %} {{ name|tag_attr:value }}{% endfor %}
I'm not sure if this needs to be a built-in filter, but I wouldn't object to
it. And unless there are other use cases for the "is" comparator, I'm -0 on
that.
Shai.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
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/2289024.WWdrQMz8hH%40deblack.
For more options, visit https://groups.google.com/d/optout.
