Re: Global Variables in OOP and Python
- From: Gary Herron <gherron@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 18:03:55 -0800
newbie wrote:
That form is deprecated. Better (and certainly clearer to any reader of the code) is to leave them in the module.Hello,
I have questions about global variables in OOP (in general) and Python (in specific). I understand (I think) that global variables are generally not a good idea. However, if there are variables that need to be accessed by a number of classes that exists in separate namespaces (files), what would be the best way to do this?
So far, I have approached the problem by making the variables attributes of one class and passing instances of the class as variables to the other class' methods.
The other way I thought of is to create a separate class that consists of the variables and to use the
from <file name> import *
Define a module, say Parameters, that defines any number of variables containing useful values. Then
import Parameters
wherever you want and refer to
Parameters.a
and
Parameters.b
You can even add runtime parameters (say options and paths from the command line) to the module during your initialization code, and those will be available wherever Parameters is imported:
Parameters.xyzzy = 'whatever'
Parameters.startDirectory = os.getcwd() # Get working directory at startup
(Even if the import of Parameters in some file occurs before the initialization code has a chance to run.)
Gary Herron
in all of the files (namespaces) where it is needed.
Is there a better way?
Are the two ideas presented above acceptable? If so, is one better than the other from an OOP POV?
.
- References:
- Global Variables in OOP and Python
- From: newbie
- Global Variables in OOP and Python
- Prev by Date: python coding contest
- Next by Date: Re: List index method for complex list item types?
- Previous by thread: Re: Global Variables in OOP and Python
- Next by thread: Re: Global Variables in OOP and Python
- Index(es):
Relevant Pages
|
