[ python-Bugs-1542166 ] global variable: multiple id()-addresses
SourceForge.net
noreply at sourceforge.net
Thu Aug 17 20:54:16 CEST 2006
Bugs item #1542166, was opened at 2006-08-17 18:37
Message generated for change (Comment added) made by gbrandl
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1542166&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.4
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Frank R. Schaefer (fschaef)
Assigned to: Nobody/Anonymous (nobody)
Summary: global variable: multiple id()-addresses
Initial Comment:
The **attachment** contains an example where one single
global variable appears at two different positions
when applying the 'id(...)' function.
The following files are attached:
core.py: contains the definition of the global
variable, two example functions, and
a minimal class definition.
test.py: a test program displaying that the global
variable in core.py has two addresses.
result.txt: the output of the test.py procedure.
In practical this means that a variable
'my_module.global_var' may refer to two
different objects!
----------------------------------------------------------------------
>Comment By: Georg Brandl (gbrandl)
Date: 2006-08-17 18:54
Message:
Logged In: YES
user_id=849994
In not_so_simple(), you *reassign* global_var. That means
that it is bound to a different object afterwards.
The name "global_var" you imported into the test module,
however, is bound to the original global_var object, and
this binding will not change. If that's not what you want,
you'll have to do "import core" and refer to "core.global_var".
Additionally, let me point out that using "global" to
declare a name as global in a function that does not
reassign that name is unnecessary.
Closing as Invalid.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1542166&group_id=5470
More information about the Python-bugs-list
mailing list