Jeff McNeil <j...@jmcneil.net> writes: > Thank you! It was tp_base that was confusing me. The tp_bases member > makes sense as Python supports multiple inheritance. It wasn't > immediately clear that tp_base is there for single inheritance > reasons. It's all quite clear now. > > Is that an optimization of sorts?
I think it's a compatibility thing because types didn't acquire multiple inheritance until the new-style class stuff started happening in, ummm..., Python 2.2, I think. This is rampant speculation. Please correct me. -- [mdw] -- http://mail.python.org/mailman/listinfo/python-list
