def maker(n):
def action(x):
return x ** n
return action
f = maker(2)
print(f)
print(f(3))
print(f(4))
g = maker(3)
print(g(3))
print(f(3)) # still remembers 2
Why does the nested function remember the first value 2
even though maker()
has returned and exited by the time action()
is called?
You can see it as all the variables originating in the parent function being replaced by their actual value inside the child function. This way, there is no need to keep track of the scope of the parent function to make the child function run correctly.
See it as "dynamically creating a function".
def maker(n):
def action(x):
return x ** n
return action
f = maker(2)
--> def action(x):
--> return x ** 2
This is basic behavior in python, it does the same with multiple assignments.
a = 1
b = 2
a, b = b, a
Python reads this as
a, b = 2, 1
It basically inserts the values before doing anything with them.
You are basically creating a closure.
In computer science, a closure is a first-class function with free variables that are bound in the lexical environment. Such a function is said to be "closed over" its free variables.
Related reading: Closures: why are they so useful?
A closure is simply a more convenient way to give a function access to local state.
From http://docs.python.org/reference/compound_stmts.html:
Programmer’s note: Functions are first-class objects. A 'def' form executed inside a function definition defines a local function that can be returned or passed around. Free variables used in the nested function can access the local variables of the function containing the def. See section Naming and binding for details.
You are defining TWO functions. When you call
f = maker(2)
you're defining a function that returns twice the number, so
f(2) --> 4
f(3) --> 6
Then, you define ANOTHER DIFFERENT FUNCTION
g = maker(3)
that return three times the number
g(3) ---> 9
But they are TWO different functions, it's not the same function referenced, each one it's a independent one. Even in the scope inside the function 'maker' are called the same, is't not the same function, each time you call maker()
you're defining a different function. It's like a local variable, each time you call the function takes the same name, but can contain different values.
In this case, the variable 'action' contains a function (which can be different)
That is what's called "closure". Simply put, for most if not all programming languages that treat functions as first-class object, any variables that are used within a function object are enclosed (i.e. remembered) so long as the function is still alive. It is a powerful concept if you know how to make use of it.
In your example, the nested action
function uses variable n
so it forms a closure around that variable and remembers it for later function calls.
Let’s look at three common reasons for writing inner functions.
1. Closures and Factory Functions
The value in the enclosing scope is remembered even when the variable goes out of scope or the function itself is removed from the current namespace.
def print_msg(msg):
"""This is the outer enclosing function"""
def printer():
"""This is the nested function"""
print(msg)
return printer # this got changed
Now let's try calling this function.
>>> another = print_msg("Hello")
>>> another()
Hello
That's unusual. The print_msg()
function was called with the string "Hello"
and the returned function was bound to the name another
. On calling another()
, the message was still remembered although we had already finished executing the print_msg()
function. This technique by which some data ("Hello"
) gets attached to the code is called closure in Python.
So what are closures good for? Closures can avoid the use of global values and provides some form of data hiding. It can also provide an object oriented solution to the problem. When there are few methods (one method in most cases) to be implemented in a class, closures can provide an alternate and more elegant solutions. Reference
2. Encapsulation :
General concept of encapsulation is to hide and protect inner world from Outer one, Here inner functions can be accessed only inside the outer one and are protected from anything happening outside of the function.
3. Keepin’ it DRY
Perhaps you have a giant function that performs the same chunk of code in numerous places. For example, you might write a function which processes a file, and you want to accept either an open file object or a file name:
def process(file_name):
def do_stuff(file_process):
for line in file_process:
print(line)
if isinstance(file_name, str):
with open(file_name, 'r') as f:
do_stuff(f)
else:
do_stuff(file_name)
For more you can refer this blog.
Because at the time when you create the function, n
was 2
, so your function is:
def action(x):
return x ** 2
When you call f(3), x
is set to 3
, so your function will return 3 ** 2
People answered correctly about the closure, that is: the valid value for "n" inside action is the last value it had whenever "maker" was called.
One ease way to overcome this is to make your freevar (n) a variable inside the "action" function, which receives a copy of "n" in the moment it is run:
The easiest way to do this is to set "n" as a parameter whose default value is "n" at the moment of creation. This value for "n" stays fixed because default parameters for a function are stored in a tuple which is an attribute of the function itself (action.func_defaults in this case):
def maker(n):
def action(x, k=n):
return x ** k
return action
Usage:
f = maker(2) # f is action(x, k=2)
f(3) # returns 3^2 = 9
f(3,3) # returns 3^3 = 27
One use is to return a function that maintains a parameter.
def outer_closure(a):
# parm = a <- saving a here isn't needed
def inner_closure():
#return parm
return a # <- a is remembered
return inner_closure
# set parm to 5 and return address of inner_closure function
x5 = outer_closure(5)
x5()
>5
x6 = outer_closure(6)
x6()
>6
# x5 inner closure function instance of parm persists
x5()
>5
When you create a function with the def keyword, you are doing exactly that: you are creating a new function object and assigning it to a variable. In the code you gave you are assigning that new function object to a local variable called action.
WHen you call it a second time you are creating a second function object. So f points to the first function object (square-the-value) and g points to the second function object (cube-the-value). When Python sees "f(3)" it takes it to means "execute the function object pointed to be variable f and pass it the value 3". f and g and different function objects and so return different values.
来源:https://stackoverflow.com/questions/2005956/how-do-nested-functions-work-in-python