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 steven.daprano
Recipients Claudiu.Popa, belopolsky, christian.heimes, eric.snow, ethan.furman, ionelmc, jedwards, llllllllll, r.david.murray, steven.daprano, terry.reedy
Date 2015-04-19.19:29:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This bug report seems to be completely based on a false premise. In the very first message of this issue, Ionel says:

"it return True even if __call__ is actually an descriptor that raise AttributeError (clearly not callable at all)."

but that is wrong. It *is* callable, and callable() is correct to return True. If you look at the stack trace, the __call__ method (function/property, whatever you want to call it) is called, and it raises an exception. That is no different from any other method or function that raises an exception.

It is wrong to think that raising AttributeError *inside* __call__ makes the object non-callable.

Ionel, I raised these issues on Python-list here:

but you haven't responded to them.
Date User Action Args
2015-04-19 19:29:33steven.dapranosetrecipients: + steven.daprano, terry.reedy, belopolsky, christian.heimes, ionelmc, r.david.murray, Claudiu.Popa, ethan.furman, eric.snow, llllllllll, jedwards
2015-04-19 19:29:33steven.dapranosetmessageid: <>
2015-04-19 19:29:33steven.dapranolinkissue23990 messages
2015-04-19 19:29:33steven.dapranocreate