Terry J. Reedy <tjre...@udel.edu> added the comment:
I agree with Steven's more careful analysis and with canning 'pseudo'. Current suggestion. A *future statement*, "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 *__future__ module* documents the possible values of *feature*. Cross reference *future statement to <reference/simple_stmts.html#future-statements> and *__future__ module* to its doc chapter. The first sentence above is based on the first sentence of the future statement doc. ---------- _______________________________________ 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
