This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author LambertDW
Recipients LambertDW, georg.brandl
Date 2008-12-04.04:34:56
SpamBayes Score 6.0890807e-07
Marked as misclassified No
Message-id <1228365298.64.0.945304656984.issue4517@psf.upfronthosting.co.za>
In-reply-to
Content
http://docs.python.org/dev/3.0/reference/datamodel.html#special-lookup

(After fixing the link to http://docs.python.org/3.0 at http://www.python.org/doc/ (and likewise the http://docs.python.org/whatsnew/3.0.html link.)...

The comment that __getattribute__ is "Called unconditionally to 
implement attribute accesses for instances of the class" gave me hope 
that some combination of "meta" "super" and "sub" might let me access 
__getattribute__ for expression eval('obj + another_object') despite the 
special notes.  I realize now the truth is that

"__getattribute__ is NEVER accessible in pure python code when the code 
uses the syntax of a unary or binary operator such as a+b, ~a, len(a)."
See most of the functions in this manual section.
Also name hash, which doesn't find much explicit use but could well be 
the most used python functionality.  Find a smooth way to replace my 
NEVER since code can obviously access __getattribute__ from the special 
function.

Thank you, and great work!
History
Date User Action Args
2008-12-04 04:34:59LambertDWsetrecipients: + LambertDW, georg.brandl
2008-12-04 04:34:58LambertDWsetmessageid: <1228365298.64.0.945304656984.issue4517@psf.upfronthosting.co.za>
2008-12-04 04:34:58LambertDWlinkissue4517 messages
2008-12-04 04:34:56LambertDWcreate