Hi,
Am Sat, 31 Jan 2015 22:36:05 +0100
schrieb Aymeric Augustin <aymeric.augus...@polytechnique.org>:
> I suspect it has to do with {% if %} being interpreted at runtime
> while {% block %} is interpreted at compile time.
>
> I never investigated this fully. If someone does, I’m interested :-)
This was my guess as well. However, if this indeed is the reason, then
a {% block … if … %} syntax would make it impossible to interpret
blocks at compile time, and I don't think Markus' proposal (or the {%
if %}{% block %} syntax, which I do like more than {% block if %}) is
worth that effort.
Raphael
--
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/20150201145722.76fae6d0%40arlen.
For more options, visit https://groups.google.com/d/optout.
pgpE_TMS5x3Re.pgp
Description: Digitale Signatur von OpenPGP
