Hi Neal,
[EMAIL PROTECTED] wrote:
> The code doesn't handle all the cases (e.g., nested functions), but
> gives you an idea of what can be done and where to look for the info
> (ie, in the stack frame and how to parse the byte codes to some
> extent). For nested functions, look in co_consts.
>
>
On Oct 7, 2:47 pm, "Francesco Guerrieri" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Today I've been thinking a bit about the "python internals". Inspired
> by this recipe:http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/66062
> I found out a little problem which haven't been able to solve.
> In sh
Hi,
Today I've been thinking a bit about the "python internals". Inspired
by this recipe:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/66062
I found out a little problem which haven't been able to solve.
In short, is there a way to find out how a given name lookup was started?
It is not
