Ionel Cristian Mărieș added the comment: On Mon, Apr 20, 2015 at 5:42 PM, Raymond Hettinger <rep...@bugs.python.org> wrote:
> > 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. > There is one use case: a lazy object proxy (there are some examples in the earlier replies). Eric proposed a CallableProxy/NonCallableProxy dichtonomy but I don't really like that API (feels wrong and verbose). > Please stop using the bug tracker to post li Sorry about that, I've replied through email and wasn't aware of bugtracker etiquette. The bugtracker doesn't have a nice way to reply to messages and it's atrocious on a mobile device. ---------- _______________________________________ 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
