When is the existence of nonlocal variables checked?

You can see what the scope of b knows about free variables (available for binding) from the scope of a, like so:

import inspectprint( "let's begin" )def a():    if False:        x = 10    def b():        print(inspect.currentframe().f_code.co_freevars)        nonlocal x        x = 20    b()a()

Which gives:

let's begin('x',)

If you comment out the nonlocal line, and remove the if statement with x inside, the you'll see the free variables available to b is just ().

So let's look at what bytecode instruction this generates, by putting the definition of a into IPython and then using dis.dis:

In [3]: import disIn [4]: dis.dis(a)  5           0 LOAD_CLOSURE             0 (x)              2 BUILD_TUPLE              1              4 LOAD_CONST               1 (<code object b at 0x7efceaa256f0, file "<ipython-input-1-20ba94fb8214>", line 5>)              6 LOAD_CONST               2 ('a.<locals>.b')              8 MAKE_FUNCTION            8             10 STORE_FAST               0 (b) 10          12 LOAD_FAST                0 (b)             14 CALL_FUNCTION            0             16 POP_TOP             18 LOAD_CONST               0 (None)             20 RETURN_VALUE

So then let's look at how LOAD_CLOSURE is processed in ceval.c.

TARGET(LOAD_CLOSURE) {    PyObject *cell = freevars[oparg];    Py_INCREF(cell);    PUSH(cell);    DISPATCH();}

So we see it must look up x from freevars of the enclosing scope(s).

This is mentioned in the Execution Model documentation, where it says:

The nonlocal statement causes corresponding names to refer to previously bound variables in the nearest enclosing function scope. SyntaxError is raised at compile time if the given name does not exist in any enclosing function scope.

First, understand that python will check your module's syntax and if it detects something invalid it raises a SyntaxError which stops it from running at all. Your first example raises a SyntaxError but to understand exactly why is pretty complicated although it is easier to understand if you know how __slots__ works so I will quickly introduce that first.

When a class defines __slots__ it is basically saying that the instances should only have those attributes so each object is allocated memory with space for only those, trying to assign other attributes raises an error

class SlotsTest:    __slots__ = ["a", "b"]x = SlotsTest()x.a = 1 ; x.b = 2x.c = 3 #AttributeError: 'SlotsTest' object has no attribute 'c'

The reason x.c = 3 can't work is that there is no memory space to put a .c attribute in.

If you do not specify __slots__ then all instances are created with a dictionary to store the instance variables, dictionaries do not have any limitations on how many values they contain

class DictTest:    passy = DictTest()y.a = 1 ; y.b = 2 ; y.c = 3print(y.__dict__) #prints {'a': 1, 'b': 2, 'c': 3}

Python functions work similar to slots. When python checks the syntax of your module it finds all variables assigned (or attempted to be assigned) in each function definition and uses that when constructing frames during execution.

When you use nonlocal x it gives an inner function access to a specific variable in the outer function scope but if there is no variable defined in the outer function then nonlocal x has no space to point to.

Global access doesn't run into the same issue since python modules are created with a dictionary to store its attributes. So global x is allowed even if there is no global reference to x