[issue18244] singledispatch: When virtual-inheriting ABCs at distinct points in MRO, composed MRO is dependent on haystack ordering
Guido van Rossum
report at bugs.python.org
Thu Jun 27 00:43:28 CEST 2013
Guido van Rossum added the comment:
Wow. This is heady stuff. I can't say I totally get every detail, so I'll just pick on some things you wrote.
In particular, I'm not sure I agree that there should be a conflict when there are two applicable base classes with a different dispatch if one of them is explicit in the MRO and the other isn't. After all, it both were explicit in the MRO the first one there would be picked, right? And virtual base classes are considered to appear after explicit base classes, right? (Or not?)
I do think the new approach is better (the extra code doesn't bother me), and I may be convinced yet that you made the right choice in the above case.
I have some trivial review comments on your patch to, will send those via Rietveld.
----------
nosy: +gvanrossum
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18244>
_______________________________________
More information about the Python-bugs-list
mailing list