Since "free variable" is defined in 4.2.1. Binding of names, I suggest also defining a "cell variable", as any local variable whose name is resolved to that scope in some enclosed scope.
Also, the term "free variable" is used elsewhere in the docs, where it means that the variable is resolved in an enclosing function scope, and does not include if the variable is resolved in the module scope.
The closure argument specifies a closure–a tuple of cellvars. It’s only valid when the object is a code object containing free variables. The length of the tuple must exactly match the number of free variables referenced by the code object.
Use the name 'func' to refer to the function involved. func.__code__ is the object given to exec().
Instead of 'cellvars', say 'bindings for free variables in 'func'.' Refer to new 'Cell objects' section of the Type Hierarchy.
The bindings are in the same order as the names of the free variables found in code.co_freevars.
The bindings can be found in func.__closure.
func.__closure__ reflects values of the free variables at the time exec is called, which may have changed since func was created.
Bindings in closure can be modified by the code if the variable names are declared nonlocal in func. If 'closure' is func.__closure__, then the 'func' free variables will have changed.
Refer to new 'Cell Objects' section in the Type Hierarchy for details.
Add a section for 'Cell Objects' under 'Internal types'.
The name of the class is 'cell', and the class is available in types.CellType.
It represents the binding of a free or cell variable.
It may have a current value (any Python object), or it may be empty.
cell() is an empty cell. cell(obj) is a cell with obj as its current value.
cell.cell_contents is a writable attribute returning the current value, if any, or raising ValueError if empty. It may be assigned a new value or deleted (without raising an exception if already empty).
Cells may be compared by their values. Empty cells compare < non-empty cells.
Mention that Frame objects have class 'frame', which is types.FrameType. There is no explicit constructor.
User-defined functions section:
Add an id=user-defined-functions tag to the HTML so that it can be linked to as a fragment.
Under closure, refer to the new 'Cell objects' section, instead of the later paragraph about cells.
Cell variable
Since "free variable" is defined in 4.2.1. Binding of names, I suggest also defining a "cell variable", as any local variable whose name is resolved to that scope in some enclosed scope. Also, the term "free variable" is used elsewhere in the docs, where it means that the variable is resolved in an enclosing function scope, and does not include if the variable is resolved in the module scope.
exec(..., closure=...)
func.__code__
is the object given toexec()
.code.co_freevars
.func.__closure
.func.__closure__
reflects values of the free variables at the timeexec
is called, which may have changed sincefunc
was created.closure
can be modified by the code if the variable names are declared nonlocal infunc
. If 'closure' isfunc.__closure__
, then the 'func' free variables will have changed.Type Hierarchy
Add a section for 'Cell Objects' under 'Internal types'.
types.CellType
.cell()
is an empty cell.cell(obj)
is a cell withobj
as its current value.cell.cell_contents
is a writable attribute returning the current value, if any, or raising ValueError if empty. It may be assigned a new value or deleted (without raising an exception if already empty).Mention that Frame objects have class 'frame', which is
types.FrameType
. There is no explicit constructor.User-defined functions section:
inspect.getmembers
Add entry for 'closure' under 'function'. Use same text as above in the user-defined functions section.
Entry for 'co_cellvars' under 'code', should read 'contained scopes' instead of 'containing scopes'. And it is only for names in 'co_varnames'.