From 240e26b3b56740e528dc2a76b8f3416642ded503 Mon Sep 17 00:00:00 2001 From: Smart <47581948+hellocoldworld@users.noreply.github.com> Date: Wed, 16 Jun 2021 10:36:21 -0300 Subject: [PATCH] Address #10648 Postponed evaluation of annotations was deferred to 3.11 - update the docs. --- docs/source/runtime_troubles.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/runtime_troubles.rst b/docs/source/runtime_troubles.rst index 39558464cf55..34d9dc795f0d 100644 --- a/docs/source/runtime_troubles.rst +++ b/docs/source/runtime_troubles.rst @@ -9,7 +9,7 @@ and explains how to get your code running again. Generally speaking, we have three tools at our disposal: * For Python 3.7 through 3.9, use of ``from __future__ import annotations`` - (:pep:`563`), made the default in Python 3.10 and later + (:pep:`563`), made the default in Python 3.11 and later * Use of string literal types or type comments * Use of ``typing.TYPE_CHECKING`` @@ -47,7 +47,7 @@ Future annotations import (PEP 563) ----------------------------------- Many of the issues described here are caused by Python trying to evaluate -annotations. From Python 3.10 on, Python will no longer attempt to evaluate +annotations. From Python 3.11 on, Python will no longer attempt to evaluate function and variable annotations. This behaviour is made available in Python 3.7 and later through the use of ``from __future__ import annotations``.