On Wed, Feb 10, 2016 at 7:25 AM, Tim Graham wrote:
> The introduction to the admin in the docs [0] reads:
>
> "One of the most powerful parts of Django is the automatic admin
>> interface. It reads metadata in your model to provide a powerful and
>> production-ready
The introduction to the admin in the docs [0] reads:
"One of the most powerful parts of Django is the automatic admin interface.
> It reads metadata in your model to provide a powerful and production-ready
> interface that content producers can immediately use to start adding
> content to the
Hi everyone,
The chosen fix[1] unfortunately introduced a new regression[2].
It looks like the behavior described in the previous ticket was possible
with
Django 1.8 under certain circumstances[3] where the abstract models defined
in a foreign application were derived as concrete models in
I see this was the intention from the very beginning as documented here
[1], but wasn't my initial take. I guess it is debatable. In any case
updating the documentation to clarify it would be helpful.
[1]
Did you try looking through git blame and old tickets to find the reason
for it? The issue is raised on https://code.djangoproject.com/ticket/11078.
On Monday, February 8, 2016 at 11:19:02 PM UTC-5, Aron Podrigal wrote:
>
> Hi,
>
> While going through the code for ModelBase I came across the
Woop, I forgot the link for [1] Here it comes.
[1]
https://groups.google.com/forum/#!msg/django-developers/QRvSCTM4WDo/Nehuqfb8BgAJ
On Tue, Feb 9, 2016 at 4:26 AM, Aron Podrigal
wrote:
> While going through the code for ModelBase for reviewing [1] it is unclear
> to
While going through the code for ModelBase for reviewing [1] it is unclear
to me when inheriting from 2 Abstract models which define Managers, if the
concrete model should use the first manager according to the creation
counter or it should follow the MRO. I would expect the following test to