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 rhettinger
Recipients Claudiu.Popa, belopolsky, christian.heimes, eric.snow, ethan.furman, ionelmc, jedwards, llllllllll, r.david.murray, rhettinger, steven.daprano, terry.reedy
Date 2015-04-20.14:42:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> My point was about consistency in descriptor handling, not consistency
> of fault (eg: broken everywhere). I don't understand why that's not 
> clear here.

That is clear but also isn't sufficient motivation.  The proposed change is unnecessary and not rooted in real use cases.  It is a semantic change to a long-standing view that callable() means having a __call__ method.

> The big idea here is to harmonize capability checking with descriptor handling.

That isn't what Guido intended when he designed the capability checking.  He has a remarkably good instinct for avoiding language complexity when there aren't clear-cut benefits.

> http://blog.ionelmc.r

Please stop using the bug tracker to post links to your blog.
Date User Action Args
2015-04-20 14:42:02rhettingersetrecipients: + rhettinger, terry.reedy, belopolsky, christian.heimes, ionelmc, steven.daprano, r.david.murray, Claudiu.Popa, ethan.furman, eric.snow, llllllllll, jedwards
2015-04-20 14:42:02rhettingersetmessageid: <>
2015-04-20 14:42:02rhettingerlinkissue23990 messages
2015-04-20 14:42:02rhettingercreate