Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
> The oddity I came around is the simple case of mixins with > different parameters, where both are derived from 'object'. > It is obvious, that such a class has to comply to the parents > call interface - here object - when to be used standalone. BUT when > I ignore this and set intentionally a parameter - for test-purposes > of mixins only - the resolution algorithm seems to normalize both for the > final call without parameters - as soon as one of the mixins is a > non-parameter call. This is independent from the inheritance order > for the derived class. Sorry, this isn't a bug. In may be inconvenient but it is intrinsic to how cooperative multiple inheritance works. FWIW, the techniques for managing parameter passing are covered in this blog post: https://rhettinger.wordpress.com/2011/05/26/super-considered-super/ ---------- nosy: +rhettinger resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38262> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
