[Python-Dev] Attribute lookup ambiguity (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Tue Mar 23 01:30:15 CET 2010
- Previous message: [Python-Dev] Attribute lookup ambiguity
- Next message: [Python-Dev] Attribute lookup ambiguity
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Pascal Chambon wrote:
I don't follow you there - in my mind, the default getattribute could simply have wrapped all its operations inside soem kind of "try..catch AttributeError:" mechanism, and thus been able to fallback to getattr in any way.
But then it would be incorrect to say that "getattribute raises an exception".
When we say that a function raises an exception, we normally mean that the exception propagates out of the function and can be seen by the caller, not that it was raised and caught somewhere inside the function.
-- Greg
- Previous message: [Python-Dev] Attribute lookup ambiguity
- Next message: [Python-Dev] Attribute lookup ambiguity
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]