[issue15435] Strange behavior when AttributeError raise inside a property get function

Yariv added the comment: Duplicate of http://bugs.python.org/issue1615 , which is open. -- nosy: +Yariv ___ Python tracker ___ ___ Pyt

[issue15435] Strange behavior when AttributeError raise inside a property get function

Nick Coghlan added the comment: Yup. It's unfortunate, but there's really nothing we can do about it - some protocols use exceptions, and if you raise an exception type that is part of the defined protocol as the result of a genuine error, then you're going to have a fun debugging exercise to

[issue15435] Strange behavior when AttributeError raise inside a property get function

Cédric Krier added the comment: The problem is that the code of the property could raise an AttributeError. So this error is not showed by the traceback. -- ___ Python tracker

[issue15435] Strange behavior when AttributeError raise inside a property get function

R. David Murray added the comment: AttributeError is how Python decides that __getattr__ should be called. I believe this is working as designed. -- nosy: +r.david.murray ___ Python tracker _

[issue15435] Strange behavior when AttributeError raise inside a property get function

New submission from Cédric Krier : When a AttributeError is raised inside the get function of a property and if the class has a __getattr__ method defined then this method is called. It is strange behavior because when looking at the traceback it looks like Python doesn't find the property. --