Steven D'Aprano steve+comp.lang.python at pearwood.info
Mon Aug 13 04:24:46 EDT 2012

• Previous message (by thread): Official reason for omitting inspect.currentcallable() ?
• Next message (by thread): Official reason for omitting inspect.currentcallable() ?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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

---

• Previous message (by thread): Official reason for omitting inspect.currentcallable() ?
• Next message (by thread): Official reason for omitting inspect.currentcallable() ?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list