On Mon, Dec 9, 2013 at 6:31 PM, Alan Bawden <a...@scooby-doo.csail.mit.edu> wrote: > I don't believe that this was done for any deep principled reason, but > rather it was just permitted because the algorithm for computing method > resolution order didn't actually care whether there were inheritance > cycles -- it still terminated and returned an ordered list of component > classes.
How does that work, exactly? How do you have a class inherit (ultimately) from itself, and how does that impact the component class list? ChrisA -- https://mail.python.org/mailman/listinfo/python-list
