On 15 June 2015 at 21:34, Florian Apolloner <[email protected]> wrote:
> > > On Monday, June 15, 2015 at 7:07:38 PM UTC+2, Rick van Hattem (wolph) > wrote: >> >> Would anyone oppose a pull request like this? >> > > Yes, it is highly backwards incompatible for not much gain, I am also > usually just fine with one/two fields for list_display. You could just use > your own admin subclass for that. > Can you clarify on that? I don't see the backwards incompatibility here. Upgrading or downgrading Django won't break this in any way and it won't change the way people can override the list_display default value so by definition it's not breaking either forwards or backwards compatibility. It changes behaviour and looks, but it doesn't break anything. The discussion here shouldn't be whether you can or cannot fix it yourself (obviously, you can, that's not the issue), it's what a good/sane default would be. For brand new Django users, would it be more convenient to have 1 column or just all local columns and make it slightly more usable? ~wolph -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJAwA%3Dz08kMH9Wv_iANf-byofidSEsEhN5eqdVA63NJvAMFtBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
