<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">@Chris</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">thanks for pointing out this self-reference, I am still not sure whether this is really suprising to me, but at least I am still not done with thinking about it, so probably it is<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">@Ned</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">As I understood it, the MRO is not only for searching attributes - there it is indeed impressively redundant to put the same class twice into the MRO, thanks for pointing that out - but also for the hierarchy of the super() command</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">@all</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">thank you all for your comments and help. My current conclusion is that I will read about the C3 algorithm in crucially more detail and what it in fact is trying to solve ... and eventually may come back</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">best,</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(0,0,0)">Stephan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 10 December 2015 at 21:43, Ned Batchelder <span dir="ltr"><<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
On 12/10/15 3:03 PM, Stephan Sahm wrote:<br>
<blockquote type="cite">
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000">(B, mixin,
A, mixin, object)</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000">or in the
simpler, more trivial version</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000">(B, object,
A, object)</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:#000000">As you
haven't mentioned this as a possibility at all, I guess having a
class twice in this list produces some weird behaviour I do not
know about yet - if someone can point out, that would be great.</div>
</blockquote></span>
The MRO is a list of classes to search for attributes. There's no
point in having a class listed twice. The second occurrence would
never be used, because any attribute it could provide would be found
on the first occurrence of the class.<span class="HOEnZb"><font color="#888888"><br>
<br>
--Ned.<br>
</font></span></div>
<br>_______________________________________________<br>
Python-ideas mailing list<br>
<a href="mailto:Python-ideas@python.org">Python-ideas@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-ideas" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-ideas</a><br>
Code of Conduct: <a href="http://python.org/psf/codeofconduct/" rel="noreferrer" target="_blank">http://python.org/psf/codeofconduct/</a><br></blockquote></div><br></div>