tristanlatr
commented
10 months ago Here are the relevant parts of the specifications:
-
When the new syntax is used, a new lexical scope is introduced (called def695 scope), and this scope includes the type parameters. Type parameters can be accessed by name within inner scopes. As with other symbols in Python, an inner scope can define its own symbol that overrides an outer-scope symbol of the same name.
-
the new scopes behave like function scopes, except for a number of minor differences listed below.
- If a def695 scope is immediately within a class scope, or within another def695 scope that is immediately within a class scope, then names defined in that class scope can be accessed within the def695 scope. (Regular functions, by contrast, cannot access names defined within an enclosing class scope.)
- Names bound within def695 scopes cannot be rebound with a nonlocal statement in nested scopes.
- yield, yield from await and the walrus operator cannot be used directly within a def695 scope.
-
Eagerly evaluated values: The type parameters of generic type aliases The type parameters and annotations of generic functions The type parameters and base class expressions of generic classes
-
Lazily evaluated values: The value of generic type aliases The bounds of type variables The constraints of type variables
-
Type parameters are visible to other type parameters declared elsewhere in the list. This allows type parameters to use other type parameters within their definition.
-
A compiler error or runtime exception is generated if the definition of an earlier type parameter references a later type parameter even if the name is defined in an outer scope.
-
Type parameters declared using the new syntax will not appear within the dictionary returned by globals() or locals().
https://peps.python.org/pep-0695/