As somebody who ran across this bug a few weeks ago (using comment to
capture the output). I _really_ wish the behavior would die.
Personally I would be in favor of dropping output when there is an "as"
attribute, if somebody depends on it in the 1.3 timeframe there could be
a setting that was enabled to support the legacy behavior.
from django.template.defaulttags import cycle
cycle.ALWAYS_OUTPUT = True
Or some other evil bit, to allow the "few" people who depend on the
legacy behavior to have access and the rest of us to move forward.
On 7/7/10 9:51 AM, David De La Harpe Golden wrote:
On 07/07/10 17:27, Bill Freeman wrote:
I agree that the "as" clause makes me expect it to render nothing, but it
has worked this way at least back to 1.0, so I guess changing it is not
an option.
hypothetical, could add an "only" clause maybe to preserve backward compat?
{% cycle 'odd' 'even' as somevar only %}
Though that breaks regularity of "as"-using tags. Up to the django guys
I suppose. Ho hum.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
