Well, the whole point was to clean up my code:
Actually this is what I have:
Class A:
def A_Func(self, p_param):
.....
Class B:
def A_Func(self):
.....
Class C (A,B):
A.__init__(self)
B.__init__(self)
Class D (A,B):
A.__init__(self)
B.__init__(self)
Where A is a wxWidget class and B a "Common/utility" class which I wanted to
factorize (and yes, inheritance was not mandatory here, just simpler)
My common class does have an A_Func(self) while wxWidget an A_Func(self,
p_param) ==> I actually got the error calling A_Func(self) as it was
checked against A_Func(self, p_param).
Regards,
Philippe
Lawrence D'Oliveiro wrote:
> In article <[EMAIL PROTECTED]>,
> "Ben Cartwright" <[EMAIL PROTECTED]> wrote:
>
>>Philippe Martin wrote:
>>
>>> I renamed A_Func(self) to fix that ... but is there a cleaner way around
>>> ?
>>
>>When using multiple inheritence, the order of the base classes matters!
>
> When you have to start worrying about complications like this, isn't
> that a sign that you're taking the whole OO thing a little too seriously?
>
> After all, technology is supposed to _solve_ problems, not create them.
> If the complications of OO are making you lose sight of your original
> problem, then maybe you should put them aside.
--
http://mail.python.org/mailman/listinfo/python-list
