Steven Hsu <hsuhaoc...@gmail.com> added the comment:
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__ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44693> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
