Gigi wrote:
> to be inaccurate. I fill a little like Leibnitz :-) . It's a curious
It's Leibniz -- unless you're in the cookie business.
I see your post for the third time, btw. What's wrong?
Peter
--
http://mail.python.org/mailman/listinfo/python-list
Terry Reedy wrote:
> "Gigi" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>>Hi,
>>In the Python documentation regarding __getattribute__ (more attribute
>>access for new style classes) it is mentioned that if __getattribute__
>>is defined __getattr__ will never be called (unless
Terry Reedy wrote:
> "Gigi" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>>Hi,
>>In the Python documentation regarding __getattribute__ (more attribute
>>access for new style classes) it is mentioned that if __getattribute__
>>is defined __getattr__ will never be called (unless
Terry Reedy wrote:
> "Gigi" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>>Hi,
>>In the Python documentation regarding __getattribute__ (more attribute
>>access for new style classes) it is mentioned that if __getattribute__
>>is defined __getattr__ will never be called (unless
"Gigi" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
> In the Python documentation regarding __getattribute__ (more attribute
> access for new style classes) it is mentioned that if __getattribute__
> is defined __getattr__ will never be called (unless called explicitely).
> H
discovered that it is not so for Python 2.3.4 on Windows at least. The
actual behavior is that if both __getattribute__ and __getattr__ methods
exist then __getattribute__ is called first, but if it raises
AttributeError then the exception will be swallowed silently and
__getattr__ will be invoke
