Using global variables in a function
You can use a global variable within other functions by declaring it as
global within each function that assigns a value to it:
globvar = 0def set_globvar_to_one(): global globvar # Needed to modify global copy of globvar globvar = 1def print_globvar(): print(globvar) # No need for global declaration to read value of globvarset_globvar_to_one()print_globvar() # Prints 1
I imagine the reason for it is that, since global variables are so dangerous, Python wants to make sure that you really know that's what you're playing with by explicitly requiring the
See other answers if you want to share a global variable across modules.
If I'm understanding your situation correctly, what you're seeing is the result of how Python handles local (function) and global (module) namespaces.
Say you've got a module like this:
# sample.pymyGlobal = 5def func1(): myGlobal = 42def func2(): print myGlobalfunc1()func2()
You might expecting this to print 42, but instead it prints 5. As has already been mentioned, if you add a '
global' declaration to
func2() will print 42.
def func1(): global myGlobal myGlobal = 42
What's going on here is that Python assumes that any name that is assigned to, anywhere within a function, is local to that function unless explicitly told otherwise. If it is only reading from a name, and the name doesn't exist locally, it will try to look up the name in any containing scopes (e.g. the module's global scope).
When you assign 42 to the name
myGlobal, therefore, Python creates a local variable that shadows the global variable of the same name. That local goes out of scope and is garbage-collected when
func1() returns; meanwhile,
func2() can never see anything other than the (unmodified) global name. Note that this namespace decision happens at compile time, not at runtime -- if you were to read the value of
func1() before you assign to it, you'd get an
UnboundLocalError, because Python has already decided that it must be a local variable but it has not had any value associated with it yet. But by using the '
global' statement, you tell Python that it should look elsewhere for the name instead of assigning to it locally.
(I believe that this behavior originated largely through an optimization of local namespaces -- without this behavior, Python's VM would need to perform at least three name lookups each time a new name is assigned to inside a function (to ensure that the name didn't already exist at module/builtin level), which would significantly slow down a very common operation.)
Each module has its own private symbol table, which is used as the global symbol table by all functions defined in the module. Thus, the author of a module can use global variables in the module without worrying about accidental clashes with a user’s global variables. On the other hand, if you know what you are doing you can touch a module’s global variables with the same notation used to refer to its functions,
A specific use of global-in-a-module is described here - How do I share global variables across modules?, and for completeness the contents are shared here:
The canonical way to share information across modules within a single program is to create a special configuration module (often called config or cfg). Just import the configuration module in all modules of your application; the module then becomes available as a global name. Because there is only one instance of each module, any changes made to the module object get reflected everywhere. For example:
x = 0 # Default value of the 'x' configuration setting
import configconfig.x = 1
import configimport modprint config.x