Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #72911 > unrolled thread

Re: strange behaivor of nested function

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: strange behaivor of nested function Chris Angelico <rosuav@gmail.com> - 2014-06-07 21:32 +1000

#72911 — Re: strange behaivor of nested function

On Sat, Jun 7, 2014 at 9:17 PM, 1989lzhh <1989lzhh@gmail.com> wrote:
> def make():
>     def jit(sig):
>         def wrap(function):
>             sig=sig[0] # unbound local error, if change to sig='' would be just fine
>             return function
>         return wrap
>     return jit
> jit=make()
> @jit('')
> def f():
>     pass
>
> It is strange that the interpreter complain about unbound local error.
> please give me some suggestion, thanks!
> Ps: I am using python 2.7

It's quite simple. You're assigning to the name 'sig' inside the
function 'wrap', which means that - in the absence of a declaration -
'sig' is a local name. But before you assign anything to it, you first
try to reference it, by subscripting it (sig[0]). Python doesn't have
a rule about pulling something in from another scope at the same time
as making it local (some languages do, and it's rather handy, but it
can only work with variable declarations), so what you're attempting
to do there simply won't work.

But it seems a little odd anyway. Why do you take the first element of
sig every time the inner function is called? Surely you want to do
that just once?

ChrisA

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web