I would agree with you about not being able to evaluate arbitrary expressions is awkward, not to mention surprising, and, because of unnecessary keyword creep, even adds clutter unnecessarily.
You may wish to take a look at Evoque Templating http://evoque.gizmojo.org/ that allows arbitrary evaluations (as well as, when needed, evaluation context restriction for security). The template syntax is really small, and easy to remember... see: http://evoque.gizmojo.org/syntax/ The simple use case you use as example would translate to something like: $if{ a == 1 } blah $else foo $fi For an example of how it can be used a django app, see: http://evoque.gizmojo.org/ext/django/ mario On Jul 13, 9:01 am, Chris <[EMAIL PROTECTED]> wrote: > Just out of curiosity, is there a reason why the templating constructs > can't evaluate arbitrary expressions? It seems terribly awkward to me > that {% if %} can only evaluate variable names, while you need the > separate operator {% ifequals %} to test for equality, and for some > reason it doesn't support {% else %}. > > I had a very simple use case where I wanted to do something like: > > {% if a == 1}blah{% else %}foo{% endif %} > > and the closest I can get is: > > {% ifequal a 1 %}blah{% endifequal %}{% ifnotequal a 1 %}foo{% > endifnotequal %} > > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
