On Jul 1, 2:34 am, Mitchell L Model <mlmli...@comcast.net> wrote: > I suspect we should have a Multiple Inheritance HOWTO, though details and > recommendations would be controversial. I've accumulated lots of abstract > examples along the lines of my question, using multiple inheritance both to > create combination classes (the kinds that are probably best done with > composition instead of inheritance) and mixins. I like mixins, and I like > abstract > classes. And yes I understand the horrors of working with a large component > library that uses mixins heavily, because I've experienced many of them, going > all the way back to Lisp-Machine Lisp's window system with very many combo > classes such as FancyFontScrollingTitledMinimizableWindow, or whatever. > Also, I understand that properties might be better instead of multiple > inheritance > for some situations. What I'm trying to do is puzzle out what the reasonable > uses > of multiple inheritance are in Python 3 and how classes and methods that > follow > them should be written.
You may be interest in my "Things to know about super": http://www.artima.com/weblogs/viewpost.jsp?thread=236275 http://www.artima.com/weblogs/viewpost.jsp?thread=236278 http://www.artima.com/weblogs/viewpost.jsp?thread=237121 -- http://mail.python.org/mailman/listinfo/python-list
