On Monday, June 15, 2015 at 11:03:07 PM UTC+2, Shai Berger wrote:
>
> (I received the message I'm replying to here with an empty subject, and
> detached from the thread. Google Groups being funny?)
>
Guess so, I didn't get an email from your reply either... that's why I
responded this slowly.
Agree this is not an appropriate default, although I could see an argument
for supporting __all__ like in forms. This isn't very hard as a third party
solution though so I'm not super keen on that idea.
M
On 15 Jun 2015 22:03, "Shai Berger" wrote:
> (I received the message I'm replying to here w
(I received the message I'm replying to here with an empty subject, and
detached from the thread. Google Groups being funny?)
On Monday 15 June 2015 22:52:09 Rick van Hattem wrote:
> On 15 June 2015 at 21:34, Florian Apolloner wrote:
> > On Monday, June 15, 2015 at 7:07:38 PM UTC+2, Rick van Hat
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 subcl
While there are several solutions to this problem, I find myself
scaffolding the Django admin every time I create a new app/model. I even
created an app to do just that (harmless
plug: https://pypi.python.org/pypi/django-admin-generator/).
Anyhow... I've wondered for some time why Django doesn'
