-
-
Notifications
You must be signed in to change notification settings - Fork 0
/
test_function_scopes.py
107 lines (85 loc) · 5.02 KB
/
test_function_scopes.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
"""Scopes and Namespaces.
@see: https://docs.python.org/3/tutorial/classes.html#scopes-and-namespaces-example
A NAMESPACE is a mapping from names to objects. Most namespaces are currently implemented as Python
dictionaries, but that’s normally not noticeable in any way (except for performance), and it may
change in the future. Examples of namespaces are: the set of built-in names (containing functions
such as abs(), and built-in exception names); the global names in a module; and the local names
in a function invocation. In a sense the set of attributes of an object also form a namespace.
The important thing to know about namespaces is that there is absolutely no relation between names
in different namespaces; for instance, two different modules may both define a function maximize
without confusion — users of the modules must prefix it with the module name.
By the way, we use the word attribute for any name following a dot — for example, in the expression
z.real, real is an attribute of the object z. Strictly speaking, references to names in modules are
attribute references: in the expression modname.func_name, modname is a module object and func_name
is an attribute of it. In this case there happens to be a straightforward mapping between the
module’s attributes and the global names defined in the module: they share the same namespace!
A SCOPE is a textual region of a Python program where a namespace is directly accessible.
“Directly accessible” here means that an unqualified reference to a name attempts to find the name
in the namespace.
Although scopes are determined statically, they are used dynamically. At any time during execution,
there are at least three nested scopes whose namespaces are directly accessible:
- the innermost scope, which is searched first, contains the local names.
- the scopes of any enclosing functions, which are searched starting with the nearest enclosing
scope, contains non-local, but also non-global names.
- the next-to-last scope contains the current module’s global names.
- the outermost scope (searched last) is the namespace containing built-in names.
BE CAREFUL!!!
-------------
Changing global or nonlocal variables from within an inner function might be a BAD
practice and might lead to harder debugging and to more fragile code! Do this only if you know
what you're doing.
"""
# pylint: disable=invalid-name
test_variable = 'initial global value'
def test_function_scopes():
"""Scopes and Namespaces Example"""
# This is an example demonstrating how to reference the different scopes and namespaces, and
# how global and nonlocal affect variable binding:
# pylint: disable=redefined-outer-name
test_variable = 'initial value inside test function'
def do_local():
# Create variable that is only accessible inside current do_local() function.
# pylint: disable=redefined-outer-name
test_variable = 'local value'
return test_variable
def do_nonlocal():
# Address the variable from outer scope and try to change it.
# pylint: disable=redefined-outer-name
nonlocal test_variable
test_variable = 'nonlocal value'
return test_variable
def do_global():
# Address the variable from very global scope and try to change it.
# pylint: disable=redefined-outer-name,global-statement
global test_variable
test_variable = 'global value'
return test_variable
# On this level currently we have access to local for test_function_scopes() function variable.
assert test_variable == 'initial value inside test function'
# Do local assignment.
# It doesn't change global variable and variable from test_function_scopes() scope.
do_local()
assert test_variable == 'initial value inside test function'
# Do non local assignment.
# It doesn't change global variable but it does change variable
# from test_function_scopes() function scope.
do_nonlocal()
assert test_variable == 'nonlocal value'
# Do global assignment.
# This one changes global variable but doesn't change variable from
# test_function_scopes() function scope.
do_global()
assert test_variable == 'nonlocal value'
def test_global_variable_access():
"""Testing global variable access from within a function"""
# Global value of test_variable has been already changed by do_global() function in previous
# test so let's check that.
# pylint: disable=global-statement
global test_variable
assert test_variable == 'global value'
# On this example you may see how accessing and changing global variables from within inner
# functions might make debugging more difficult and code to be less predictable. Since you
# might have expected that test_variable should still be equal to 'initial global value' but
# it was changed by "someone" and you need to know about the CONTEXT of who had changed that.
# So once again access global and non local scope only if you know what you're doing otherwise
# it might be considered as bad practice.