Official reason for omitting inspect.currentcallable() ?

[Steven D'Aprano]

On Sun, 12 Aug 2012 23:06:19 +0000, kj wrote:

> Is there an *explicitly stated* reason (e.g. in a PEP, or in some python
> dev list message) for why the inspect module (at least for Python 2.7)
> does not include anything like a "currentcallable()" function that would
> *stably*[1] return the currently executing callable object?

I doubt it. Should there be? "currentcallable" is not a standard function 
in any language I'm familiar with, although I may be missing something 
obvious.


-- 
Steven