Raymond Hettinger added the comment: > 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. ---------- _______________________________________ 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
