Skip to content

Commit 0363a40

Browse files
bpo-44693: Update __future__ entry in Doc/glossary.rst (GH-27349)
Replace sentence with confusing "pseudo-module" with two sentences separating future statements and the __future__ module. Co-authored-by: Terry Jan Reedy <[email protected]>
1 parent 4214f47 commit 0363a40

File tree

2 files changed

+9
-6
lines changed

2 files changed

+9
-6
lines changed

Doc/glossary.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -451,12 +451,13 @@ Glossary
451451
for best practices on working with annotations.
452452

453453
__future__
454-
A pseudo-module which programmers can use to enable new language features
455-
which are not compatible with the current interpreter.
456-
457-
By importing the :mod:`__future__` module and evaluating its variables,
458-
you can see when a new feature was first added to the language and when it
459-
becomes the default::
454+
A :ref:`future statement <future>`, ``from __future__ import <feature>``,
455+
directs the compiler to compile the current module using syntax or
456+
semantics that will become standard in a future release of Python.
457+
The :mod:`__future__` module documents the possible values of
458+
*feature*. By importing this module and evaluating its variables,
459+
you can see when a new feature was first added to the language and
460+
when it will (or did) become the default::
460461

461462
>>> import __future__
462463
>>> __future__.division
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
Update the definition of __future__ in the glossary by replacing the confusing
2+
word "pseudo-module" with a more accurate description.

0 commit comments

Comments
 (0)