I would also like to know more about the rational behind ditching the
idea of
multilinetags.
{% trans with
varname=myobject.proprety1
someothervar=myobject.some.other_property
yetanothervar=myotherobject.with_a_painfully_long_method_name
"Even with line-wrap, it's a pain to read on a single line."
%}
Forcing a Python developer to write something like this on a single
line
is borderline cruel.
Besides, it's backward compatible (I think so) and it doesn't break
syntax highlighting (in Vim at least).
+1
On Feb 18, 1:04 am, Glenn Washburn <developm...@efficientek.com>
wrote:
> Hello django devers,
>
> I'd like to reopen discussion on the multiline tag issue
> (see:https://code.djangoproject.com/ticket/8652) which was closed 3 three
> years ago as "won't fix". The last comment notes that this won't
> happen as the decision has been made many times. But there is no link
> to any discussion on this topic, so I can only assume mtredinnick's
> point two is the supposed reason for not fixing this.
>
> I've done rudimentary testing on a 6 character change in 1.3.1 to
> template.base.tags_re (add the re.S flag to the regex), which appears
> to solve the issue. So I don't see all the work which was being
> referred to in mtredinnick's point two. Perhaps the template engine
> has been rewritten since then. The only test that fails after making
> this change (in 1.3.1) is the one that explicitly tests that tgs should
> not be multiline.
>
> Since this change appears to be so low impact and such a simple
> change. Are there any reasons why this change shouldn't be included in
> django? Maybe I'm missing something.
>
> Its interesting to note thathttps://code.djangoproject.com/ticket/3888, which
> is referenced in the
> issue, is also closed as "won't fix", but appears to be allowed in
> 1.3.1. So there is a precedent for "won't fix" issues being included.
>
> -Glenn
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
