Message398122
Applying above suggestions, the first sentence of the entry "__future__" would be replaced by:
A :ref:`future statement <future>`, "from __future__ import *feature* ...", directs the compiler to compile the current module using syntax or semantics that will become standard in a future release of Python. The :mod:`__future__` module documents the possible values of *feature*.
And the confusing sentence, "A pseudo-module which programmers can use to enable new language features which are not compatible with the current interpreter." would be removed.
Can I fix this issue this way?
If confirmed, I would make a PR for this issue.
--
:ref:`future` -> https://docs.python.org/3.9/reference/simple_stmts.html#future-statements
:mod:`__future__` -> https://docs.python.org/3.9/library/__future__.html#module-__future__ |
|
Date |
User |
Action |
Args |
2021-07-24 08:36:54 | StevenHsuYL | set | recipients:
+ StevenHsuYL, terry.reedy, eric.araujo, steven.daprano, docs@python |
2021-07-24 08:36:54 | StevenHsuYL | set | messageid: <1627115814.38.0.422843973662.issue44693@roundup.psfhosted.org> |
2021-07-24 08:36:54 | StevenHsuYL | link | issue44693 messages |
2021-07-24 08:36:54 | StevenHsuYL | create | |
|