From 9a4b7c60716c761139f808caae23628355eaa1ff Mon Sep 17 00:00:00 2001 From: Larry Hastings Date: Mon, 11 Jan 2021 16:14:32 -0800 Subject: [PATCH] Clarify 649 wrt annotations inside flow control. --- pep-0649.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/pep-0649.rst b/pep-0649.rst index c5b7907b2..5c26953c6 100644 --- a/pep-0649.rst +++ b/pep-0649.rst @@ -239,11 +239,12 @@ The good news is, neither is common, and neither is considered good practice. In fact, they're rarely seen outside of Python's own regression test suite. They are: -* *Code that sets annotations from inside any kind of - flow control statement.* It's currently possible to set - module and class attributes with annotations inside an - ``if`` or ``try`` statement, and it works as one would expect. - It's untenable to support this behavior when this PEP is active. +* *Code that sets annotations on module or class attributes + from inside any kind of flow control statement.* It's + currently possible to set module and class attributes with + annotations inside an ``if`` or ``try`` statement, and it works + as one would expect. It's untenable to support this behavior + when this PEP is active. * *Code in module or class scope that references or modifies the local* ``__annotations__`` *dict directly.* Currently, when setting annotations on module or class attributes, the generated