On Jun 23, 9:16 pm, Karen Tracey <kmtra...@gmail.com> wrote:
>
> Raising some sort of error for child template content found outside of a {%
> block %} seems like a more reasonable idea. I have no idea if it's been
> asked for/considered/rejected/etc., nor how hard it would be to do. If you
> are really interested in pursuing that idea I'd first search the tracker and
> archives of this list to see if it hasn't already been discussed.
>
A similar ticket regarding enclosing child blocks with "if" statements
was closed with the statement that "this is by design."
http://code.djangoproject.com/ticket/10975
I don't really agree with the design in either case. I think tags
that are truly outside of derived blocks should create syntax errors,
and tags that surround derived blocks should somehow satisfy the
principle of least astonishment--either apply the conditional or
variable assignment when rendering or raise a syntax error, but don't
just ignore the tags silently.
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
