Raymond Hettinger added the comment:
I suggest linking to the built-in callable() function:
https://docs.python.org/3/library/functions.html#callable
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
Delgan added the comment:
I agree, it's straightforward. I just thought it could be useful to have a
proper definition in the official documentation.
For example, this question on StackOverflow actually received many views:
https://stackoverflow.com/questions/111234/what-is-a-callable
What
Raymond Hettinger added the comment:
-1 I don't think this would be an improvement. We already have a builtin
callable() function documented, and we have the documented Callable() abstract
base class, and the __call__ method is documented in the library reference. I
don't we need yet anoth
New submission from Delgan :
Hi.
Quick use case explanation about this: I would like to document my function,
stating that it accepts any "callable" object and linking to a proper
definition of such object.
For example, I'm already doing this when my function accepts a "file object".
There