Skip to content

Commit caa71f6

Browse files
committed
Wrap the test in a consistent way
1 parent ea921e8 commit caa71f6

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

docs/spec/annotations.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -224,12 +224,12 @@ definition may be expressed as a string literal, to be resolved later.
224224

225225
The string literal should contain a syntactically valid Python expression
226226
(i.e., ``compile(lit, '', 'eval')`` should succeed) that evaluates to a valid
227-
:term:`annotation expression`. Regardless of the Python version used, names within the expression are looked up in the
228-
same way as they would be looked up at runtime in Python 3.14 and higher if the
229-
annotation was not enclosed in a string literal. Thus, name lookup follows
230-
general rules (e.g., the current function, class, or module scope first, and
231-
the builtin scope last), but names defined later within the same scope can be
232-
used in an earlier annotation.
227+
:term:`annotation expression`. Regardless of the Python version used, names
228+
within the expression are looked up in the same way as they would be looked up
229+
at runtime in Python 3.14 and higher if the annotation was not enclosed in a
230+
string literal. Thus, name lookup follows general rules (e.g., the current
231+
function, class, or module scope first, and the builtin scope last), but names
232+
defined later within the same scope can be used in an earlier annotation.
233233

234234
If a triple quote is used, the string should be parsed as though it is
235235
implicitly surrounded by parentheses. This allows newline characters to be

0 commit comments

Comments
 (0)