Skip to content

Address #10648 #10655

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2021
Merged

Address #10648 #10655

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/source/runtime_troubles.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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``

Expand Down Expand Up @@ -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``.

Expand Down