Re: Official reason for omitting inspect.currentcallable() ?

From	kj <no.email@please.post>
Newsgroups	comp.lang.python
Subject	Re: Official reason for omitting inspect.currentcallable() ?
Date	2012-08-13 14:16 +0000
Organization	none
Message-ID	<k0b287$t6t$1@reader1.panix.com> (permalink)
References	<k09ctb$66t$1@reader1.panix.com> <5028b9ce$0$29867$c3e8da3$5496439d@news.astraweb.com> <mailman.3221.1344847903.4697.python-list@python.org>

Show all headers | View raw

In <mailman.3221.1344847903.4697.python-list@python.org> Chris Angelico <rosuav@gmail.com> writes:

>I'm not familiar with it by that name, but Pike's this_function is
>what the OP's describing.

You got it.

>It's a useful construct in theory when you want to write in recursion,
>which was part of the rationale behind PEP 3130 

Thank you!

kj

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Official reason for omitting inspect.currentcallable() ? kj <no.email@please.post> - 2012-08-12 23:06 +0000
  Re: Official reason for omitting inspect.currentcallable() ? Terry Reedy <tjreedy@udel.edu> - 2012-08-13 01:15 -0400
  Re: Official reason for omitting inspect.currentcallable() ? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-08-13 08:24 +0000
    Re: Official reason for omitting inspect.currentcallable() ? Chris Angelico <rosuav@gmail.com> - 2012-08-13 18:51 +1000
      Re: Official reason for omitting inspect.currentcallable() ? kj <no.email@please.post> - 2012-08-13 14:16 +0000

csiph-web