I don't understand why this conversation has had to go on for this long. The original post was in February of 2012, and it is now March of 2016. That's four years of discussion that basically boils down to a couple of purists insisting that their coding style is the only coding style, fits every possible scenario and is beautiful, while a much larger group comes up with scenarios where the given style guide is counterintuitive and difficult to read.
I think the salient fact here is that templating languages are supposed to be supersets of HTML, and as supersets should respect the native abilities of their parents. With HTML it is common and accepted to break tags with many attributes across multiple lines so that the code itself is easy to read (i.e., "visually parse", a term used frequently in this thread). This same convention extends into the Python world, where long lines can easily be broken down using parenthesis to maintain language constraints while allowing for ease of readability. In fact, PEP8 specifically prohibits lines longer than 80 characters, and even people who break that generally respect something along the lines of 99. Two Scoops will tell you that any community software should be a hard limit of 80, while internal projects can be allowed to go to 99 with group consensus. So you have a python templating language for generating HTML, two languages which both embrace multi-line statements merging together, but we can't agree that it should probably also support this? I think this conversation needs to come to a conclusion, and that conclusion should be simple. Several people have asked a very simple question of the purists: what is the "correct" way of writing tags which by nature need to be very long, without line breaks and without them being 400 characters long. If no acceptable answer can be given, we need to just implement the line break mechanic and give the developers back their whitespace. -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/06029153-7606-4047-b6a4-7d0d1b9dd04d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
