James Edwards added the comment: It seems like this issue has morphed over time.
At the beginning, it looked like you expected perfectly reasonable (but odd) definitions of __call__ attributes, where the logic inside raised an Exception, to be somehow determined to be "uncallable". This does not seem realistic at all. Then it turned into detecting whether the __call__ attribute was None or not. Fine, I guess. But towards the end, it has turned into you wanting to check whether both an instance and a class have __call__ attributes. Which doesn't seem like too much of an unreasonable change. But these changes and the proposed patch won't address your initial issue of somehow detecting that the logic inside will raise an AttributeError or that __call__ is defined, but None. ---------- nosy: +jedwards _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23990> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
