I agree with Phillip with regard to the semantics. They are semantically desirable. However, <span class="gmail_quote"><b class="gmail_sendername"></b></span>there is a patch to add a mro cache to speed up these sorts of cases on the Python tracker, originally submitted by Armin Rigo. He saw ~20% speedups, others see less. It is currently just sitting there with no apparent activity. So if the overhead of mro lookups is that bothersome, it may be well worth your time to review the patch.
<br><br>URL: <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=1700288&group_id=5470&atid=305470">http://sourceforge.net/tracker/index.php?func=detail&aid=1700288&group_id=5470&atid=305470
</a><br><br>-Kevin<br><br><br><div><span class="gmail_quote">On 6/9/07, <b class="gmail_sendername">Phillip J. Eby</b> <<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At 12:23 AM 6/10/2007 +0300, Eyal Lotem wrote:<br>>A. It will break code that uses instance.__dict__['var'] directly,<br>>when 'var' exists as a property with a __set__ in the class. I believe<br>>this is not significant.
<br>>B. It will simplify getattr's semantics. Python should _always_ give<br>>precedence to instance attributes over class ones, rather than have<br>>very weird special-cases (such as a property with a __set__).
<br><br>Actually, these are features that are both used and desirable; I've<br>been using them both since Python 2.2 (i.e., for many years<br>now). I'm -1 on removing these features from any version of Python, even
3.0.<br><br><br>>C. It will greatly speed up instance variable access, especially when<br>>the class has a large mro.<br><br>...at the cost of slowing down access to properties and __slots__, by<br>adding an *extra* dictionary lookup there.
<br><br>Note, by the way, that if you want to change attribute lookup<br>semantics, you can always override __getattribute__ and make it work<br>whatever way you like, without forcing everybody else to change *their* code.
<br><br>_______________________________________________<br>Python-Dev mailing list<br><a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/python-dev">http://mail.python.org/mailman/listinfo/python-dev
</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/jacobs%40bioinformed.com">http://mail.python.org/mailman/options/python-dev/jacobs%40bioinformed.com</a><br></blockquote></div><br>