Global module variables as default parameters

[Christoph Haas]

Hi, list...

I wondered if it's possible to use global (module) variables as default
parameters. A simple working example:

----------------------------------------
#!/usr/bin/python

globalvar = 123

def test(foo=global var):
print foo

test()
----------------------------------------

Running this script prints "123". That's what I expected.

Now I'm trying the same thing in a module context. A non-working example:

test.py
----------------------------------------
#!/usr/bin/python

import TestModule

TestModule.glob alvar = 123
TestModule.def1 ()
TestModule.def2 ()
----------------------------------------

TestModule.py
----------------------------------------
globalvar = 0

def def1():
print globalvar

def def2(foo=global var):
print foo
----------------------------------------

Running the test.py script prints "123" and "0". So accessing the globalvar
in def1() works. But if I try to use the global variable as a default
parameter in def2() it uses the default "0". What is the difference
between these two? Are there contexts of default parameters?

Thanks for any enlightenment.

Christoph

[Marc 'BlackJack' Rintsch]

In <ma************ *************** ***********@pyt hon.org>, Christoph Haas
wrote:

TestModule.py
----------------------------------------
globalvar = 0

def def1():
print globalvar

def def2(foo=global var):
print foo
----------------------------------------

Running the test.py script prints "123" and "0". So accessing the globalvar
in def1() works. But if I try to use the global variable as a default
parameter in def2() it uses the default "0". What is the difference
between these two? Are there contexts of default parameters?

Default parameters are evaluated *once* when the ``def`` is executed. So
in `def2` the value of `foo` won't be looked up when calling the function
as it is already bound to the value 0.

Ciao,
Marc 'BlackJack' Rintsch

[Peter Otten]

Christoph Haas wrote:

Hi, list...

I wondered if it's possible to use global (module) variables as default
parameters. A simple working example:

----------------------------------------
#!/usr/bin/python

globalvar = 123

def test(foo=global var):
print foo

test()
----------------------------------------

Running this script prints "123". That's what I expected.

Now I'm trying the same thing in a module context. A non-working example:

test.py
----------------------------------------
#!/usr/bin/python

import TestModule

TestModule.glob alvar = 123
TestModule.def1 ()
TestModule.def2 ()
----------------------------------------

TestModule.py
----------------------------------------
globalvar = 0

def def1():
print globalvar

def def2(foo=global var):
print foo
----------------------------------------

Running the test.py script prints "123" and "0". So accessing the
globalvar in def1() works. But if I try to use the global variable as a
default parameter in def2() it uses the default "0". What is the
difference between these two? Are there contexts of default parameters?

Yes, and that context is the function definition which is executable code,
too. Whatever the variable 'right' in a statement like

def f(left=right): ...

is bound to when the def is executed will become the default for the 'left'
argument. This should become clear when you create more than one function
with the same

>>fs = []
for i in range(3):

.... def f(i=i): print i
.... fs.append(f)
....

>>for f in fs: f()

....
0
1
2

Use a sentinel when you don't want that behaviour:

def f(foo=None):
if foo is None: foo = globalvar
# ...

Peter

[John Hunter]

>>>>"Christop h" == Christoph Haas <em***@christop h-haas.dewrites:

ChristophHi, list... I wondered if it's possible to use global
Christoph(modul e) variables as default parameters. A simple
Christophworkin g example:

Christoph----------------------------------------
Christoph#!/usr/bin/python

Christophglobal var = 123

Christophdef test(foo=global var): print foo

kwargs defaults are initialized a module load time, not at function
call time. The standard idiom is

def test(foo=None):
if foo is None: foo = globalvar
print foo

JDH

[Steve Holden]

John Hunter wrote:

>>>>>>"Christop h" == Christoph Haas <em***@christop h-haas.dewrites:

ChristophHi, list... I wondered if it's possible to use global
Christoph(modul e) variables as default parameters. A simple
Christophworkin g example:

Christoph----------------------------------------
Christoph#!/usr/bin/python

Christophglobal var = 123

Christophdef test(foo=global var): print foo

kwargs defaults are initialized a module load time, not at function
call time. The standard idiom is

def test(foo=None):
if foo is None: foo = globalvar
print foo

JDH

That's true when the functions are declared at the outer level of the
module, but don't overlook the fact that a function can be declared
inside another function or method call (and even returned as (part of)
the result of that call).

It would be more accurate to say that the default argument values are
bound when the def statement is executed.

regards
Steve
--
Steve Holden [phone] [phone]
Holden Web LLC/Ltd http://www.holdenweb.com
Skype: holdenweb http://holdenweb.blogspot.com
Recent Ramblings http://del.icio.us/steve.holden

[Christoph Haas]

Thanks to all who answered.

On Friday 22 September 2006 17:28, Marc 'BlackJack' Rintsch wrote:

Christoph Haas wrote:

TestModule.py
----------------------------------------
globalvar = 0

def def1():
print globalvar

def def2(foo=global var):
print foo
----------------------------------------

Running the test.py script prints "123" and "0". So accessing the
globalvar in def1() works. But if I try to use the global variable as
a default parameter in def2() it uses the default "0". What is the
difference between these two? Are there contexts of default
parameters?

Default parameters are evaluated *once* when the ``def`` is executed.
So in `def2` the value of `foo` won't be looked up when calling the
function as it is already bound to the value 0.

Now that you point me to it it's pretty obvious indeed. I always forget
that the 'def's are executed at load time, too.

Peter/John: in fact I already used a sentinel like you proposed as
a "workaround ". So there is just one sensible way to do it. Again.

Kindly
Christoph