From: Saiyang Gou Date: Wed, 7 Apr 2021 05:02:20 +0000 (-0700) Subject: bpo-38605: Update "Future statements" docs since PEP 563 is always enabled (GH-25236) X-Git-Tag: v3.10.0b1~381 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=1be456ae9d53bb1cba2b24fc86175c282d1c2169;p=thirdparty%2FPython%2Fcpython.git 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. --- diff --git a/Doc/reference/simple_stmts.rst b/Doc/reference/simple_stmts.rst index 2c6c90140201..3fff8484856a 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