Here's the actual code PR https://github.com/django/django/pull/2556
On Sun, Mar 13, 2016 at 1:26 AM, Martijn van Oosterhout <klep...@gmail.com> wrote: > > On 12 March 2016 at 05:31, Curtis Maloney <cur...@tinbrain.net> wrote: > > 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. >>> >> >> As pointed out by Josh in another email, I wrote a patch to permit >> multi-line tags. I asked for feedback. I got _none_. >> >> If people really wanted this feature, why didn't we hear more about it? >> What can we do to get more people to know about it, and to give more >> feedback? >> >> I would recommend you review the history of this discussion, collect the >> pros and cons, formulate a DEP, and we can go from there. >> >> I'm quite sure the patch will still work fine. >> >> > Presumably you're talking about this: > https://github.com/django/deps/pull/3/files > > I'm not sure what feedback you're expecting, but if +1's are what's > needed, then here you go: +1. > > The thing is, this feature is a nice to have but no show stopper. The > first time a developer runs into this (by trying the obvious and finding it > doesn't work), they'll check the documentation, shrug their shoulders at > the weird Django developers and get on with their job. > > Perhaps 1% will go to the effort of seeing if it has been proposed, find > it's been mentioned several times and think "someone is working on it" and > get on with their job. > > Perhaps 1% of those will note it hasn't been done yet, dig deeper and find > your proposal and the various bugs, note it's been blocked, figure it's a > lost cause and get on with their job. > > If this change requires a horde of developers waking up and calling for > it, then it's never going to happen. The current situation will however > continue to cause wasted developer time until eternity. Simply because > there is no obvious reason why it shouldn't work. It's not ambiguous, it's > not going to confuse anyone, it's just one of those little things that > makes computers just a little bit more user friendly. > > Have a nice day, > -- > Martijn van Oosterhout <klep...@gmail.com> http://svana.org/kleptog/ > > -- > 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/CADWG95v7eMb8u85PyS3MsigXMVoKs3a_H9zx8aGJBsetBaWyLQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CADWG95v7eMb8u85PyS3MsigXMVoKs3a_H9zx8aGJBsetBaWyLQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAFO84S6iJt9DCuRM5LKDWX%3DB02BUq7zBgf8TDp3-%2BrC4xGHLRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
