summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSaiyang Gou <gousaiyang@163.com>2021-04-06 22:02:20 -0700
committerGitHub <noreply@github.com>2021-04-06 22:02:20 -0700
commit1be456ae9d53bb1cba2b24fc86175c282d1c2169 (patch)
tree770c06853b297707bff2418b7daf910911301244
parent2219187cab6bca009c42b63b2f4c30b5b10c916d (diff)
downloadcpython-git-1be456ae9d53bb1cba2b24fc86175c282d1c2169.tar.gz
bpo-38605: Update "Future statements" docs since PEP 563 is always enabled (GH-25236)
Update documentation section for "Future statements" to reflect that `from __future__ import annotations` is on by default, and no features require using the future statement now.
-rw-r--r--Doc/reference/simple_stmts.rst7
1 files changed, 2 insertions, 5 deletions
diff --git a/Doc/reference/simple_stmts.rst b/Doc/reference/simple_stmts.rst
index 2c6c901402..3fff848485 100644
--- a/Doc/reference/simple_stmts.rst
+++ b/Doc/reference/simple_stmts.rst
@@ -874,14 +874,11 @@ can appear before a future statement are:
* blank lines, and
* other future statements.
-The only feature that requires using the future statement is
-``annotations`` (see :pep:`563`).
-
All historical features enabled by the future statement are still recognized
by Python 3. The list includes ``absolute_import``, ``division``,
``generators``, ``generator_stop``, ``unicode_literals``,
-``print_function``, ``nested_scopes`` and ``with_statement``. They are
-all redundant because they are always enabled, and only kept for
+``print_function``, ``nested_scopes``, ``with_statement`` and ``annotations``.
+They are all redundant because they are always enabled, and only kept for
backwards compatibility.
A future statement is recognized and treated specially at compile time: Changes