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 serhiy.storchaka
Recipients gvanrossum, hauntsaninja, kj, levkivskyi, serhiy.storchaka
Date 2020-11-16.08:38:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605515904.19.0.0548405252776.issue42102@roundup.psfhosted.org>
In-reply-to
Content
Sorry, but making builtins.callable generic looks wrong to me. It is a predicate, not a constructor. If it would be called "iscallable" instead of "callable" nobody would propose to make it generic, right? It's just a coincidence that the name of this predicate equals to the name of typing.Callable and collections.abc.Callable.

builtins.callable was removed in Python 3.0 in favor of instance check for collections.Callable. Maybe removing it again (or renaming to iscallable) would solve confusion?
History
Date User Action Args
2020-11-16 08:38:24serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, levkivskyi, hauntsaninja, kj
2020-11-16 08:38:24serhiy.storchakasetmessageid: <1605515904.19.0.0548405252776.issue42102@roundup.psfhosted.org>
2020-11-16 08:38:24serhiy.storchakalinkissue42102 messages
2020-11-16 08:38:23serhiy.storchakacreate