This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author StevenHsuYL
Recipients StevenHsuYL, docs@python, eric.araujo, steven.daprano, terry.reedy
Date 2021-07-24.08:36:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1627115814.38.0.422843973662.issue44693@roundup.psfhosted.org>
In-reply-to
Content
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__
History
Date User Action Args
2021-07-24 08:36:54StevenHsuYLsetrecipients: + StevenHsuYL, terry.reedy, eric.araujo, steven.daprano, docs@python
2021-07-24 08:36:54StevenHsuYLsetmessageid: <1627115814.38.0.422843973662.issue44693@roundup.psfhosted.org>
2021-07-24 08:36:54StevenHsuYLlinkissue44693 messages
2021-07-24 08:36:54StevenHsuYLcreate