Georg Brandl <[EMAIL PROTECTED]> added the comment:
I've changed "may bypass" to "generally bypasses". It doesn't happen for
all methods, but that's an implementation detail.
I've also added a glossary entry "special method" in r67579.
--
resolution: -> fixed
status: open -> closed
__
David W. Lambert <[EMAIL PROTECTED]> added the comment:
Yes to msg77021. However!
I'll pin the difficulty specifically to the word "may". This cost me a
lot of time.
1) Please change the phrasing you quoted to
"... implicit special method lookup bypasses the __getattribute__()
method even o
Georg Brandl <[EMAIL PROTECTED]> added the comment:
Isn't what you refer to covered by this paragraph and the following
example: "In addition to bypassing any instance attributes in the
interest of correctness, implicit special method lookup may also bypass
the __getattribute__() method even of t
David W. Lambert <[EMAIL PROTECTED]> added the comment:
>>> class c:
... def __getattribute__(self,*args):
... print('getattribute chimes in')
...
>>> c()+3
Traceback (most recent call last):
File "", line 1, in
TypeError: unsupported operand type(s) for +: 'c' and 'int'
New submission from David W. Lambert <[EMAIL PROTECTED]>:
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
