On 02/24/2012 01:29 PM, Chris Northwood wrote: > A +1 from me too, I've really felt the pain on this when doing i18n > templates, I understand the aesthetics, but the aesthetics of > obscenely long tags is also bad imo... > > On 24 February 2012 09:23, Shawn Milochik <[email protected]> wrote: >> On Fri, Feb 24, 2012 at 4:19 AM, Bradley Ayers <[email protected]> >> wrote: >>> >>> In the interest of making the wider community opinion heard, I too am +1 on >>> this, my feeling is exactly the same as Stephen. >>> >>> -- >> >> +1 >> >> I understand that a BDFL has spoken and this change isn't going to >> happen. I hate to add to the noise, but since the argument from >> popularity fallacy has been invoked, I feel the need to point out that >> many of us didn't bother to weigh in because we didn't choose to add >> to the noise. Especially after the case was so well-made by others -- >> it didn't seem necessary. >> >> Shawn >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> >
+1 If you are against truly multiline tags, consider supporting a line continuation character sequence (something like backslash in most of the programming languages) inside tags, which a poor template author can use as a last resort to make his code readable. In the docs, discourage people from going multiline. Highlight that it is the last thing to do (like PEP does). -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
