Cool!
FWIW I built the same feature as an external app called django-overextends
some time ago, you might like to compare implementations:
https://github.com/stephenmcd/django-overextends/
https://github.com/stephenmcd/django-overextends/blob/master/overextends/templatetags/overextends_tags.py
Regarding your managers: couldn't you just use inheritance explicitly?
>
> class ManagerC(ManagerA, ManagerB): pass
>
> class ModelC(ModelA, ModelB):
> objects = ManagerC()
>
> __
> Johannes
>
> Am 03.03.2010 um 23:08 schrieb Stephen McDonald:
Mar 3, 11:52 pm, Russell Keith-Magee
wrote:
> On Mon, Mar 1, 2010 at 12:40 PM, Stephen McDonald
> wrote:
> > Hi there,
>
> > I'm just getting an understanding around how managers from abstract
> > models are applied to a subclass model and it appears as though
Hi there,
I'm just getting an understanding around how managers from abstract
models are applied to a subclass model and it appears as though if a
model inherits from two abstract models that each define a manager
with the same attribute name, eg "objects", then normal mro applies
and the derived
