Curious UnboundLocalError Behavior

Matthew Franz mdfranz at gmail.com
Thu Mar 1 20:49:09 CET 2007


I had tried the global prefix in the real code (vs. the contrived
example in the post), but in the incorrect code block, which made me
think something else was up. Yes, these were supposed to be constants
that under rare circumstances were changed ;)  In the end, I  scrapped
the rebind approach, because that wasn't the behavior I wanted
either.Thanks for the help.

- mdf

On 1 Mar 2007 00:20:05 -0800, bruno.desthuilliers at gmail.com
<bruno.desthuilliers at gmail.com> wrote:
> On 28 fév, 18:15, "Matthew Franz" <mdfr... at gmail.com> wrote:
> > I'm probably fundamentally misunderstanding the way the interpreter
> > works with regard to scope, but is this the intended behavior...
> >
> (snip traceback)
>
> > import os,sys
> >
> > SOMEGLOBAL=1
> >
> > def foo():
> >     dome=False
> >     if dome:
> >         SOMEGLOBAL = 0
>
>
> This makes SOMEGLOBAL local !-)
>
> Look for the 'global' statement. Or better, try to avoid rebinding
> globals from within a function.
>
> As as side note: by convention, ALL_UPPER names denote constants.
>
> --
> http://mail.python.org/mailman/listinfo/python-list
>


-- 
Matthew Franz
http://www.threatmind.net/



More information about the Python-list mailing list