On Jul 24, 2011, at 8:39 AM, Fayaz Yusuf Khan wrote:
>
> The problem with using different mixins is that you lose out on a lot of code
> reusability. In my case, I have a 'user' column that appears in almost all
> table declarations. To have a separate mixin class for each joint-table
> inher
On Saturday 23 Jul 2011 8:24:31 PM Michael Bayer wrote:
> On Jul 23, 2011, at 7:54 AM, Fayaz Yusuf Khan wrote:
> >> When C inherits from CMixin and Timeline, Python's method resolution is
> >> going to put TMixin after Timeline, that is:
> >>
> >> (, , >> '__main__.Timeline'>, , >> 'sqlalchemy.e
