[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread Terry J. Reedy
Change by Terry J. Reedy : -- nosy: -miss-islington resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread Terry J. Reedy
Terry J. Reedy added the comment: New changeset 4ce6c5285abd78dc936ec6036e7bb964fd55d955 by Miss Islington (bot) in branch '3.9': bpo-44693: Update __future__ entry in Doc/glossary.rst (GH-27349) (GH-27358) https://github.com/python/cpython/commit/4ce6c5285abd78dc936ec6036e7bb964fd55d955 --

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread Terry J. Reedy
Terry J. Reedy added the comment: New changeset 642d873d672eb1b4ddffd99e665c54ed358a4562 by Miss Islington (bot) in branch '3.10': bpo-44693: Update __future__ entry in Doc/glossary.rst (GH-27349) (GH-27357) https://github.com/python/cpython/commit/642d873d672eb1b4ddffd99e665c54ed358a4562 -

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread Terry J. Reedy
Terry J. Reedy added the comment: New changeset 0363a4014d90df17a29042de008ef0b659f92505 by Steven Hsu in branch 'main': bpo-44693: Update __future__ entry in Doc/glossary.rst (GH-27349) https://github.com/python/cpython/commit/0363a4014d90df17a29042de008ef0b659f92505 -- __

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread miss-islington
Change by miss-islington : -- pull_requests: +25899 pull_request: https://github.com/python/cpython/pull/27358 ___ Python tracker ___ __

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread miss-islington
Change by miss-islington : -- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +25898 pull_request: https://github.com/python/cpython/pull/27357 ___ Python tracker _

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-25 Thread Steven Hsu
Change by Steven Hsu : -- keywords: +patch pull_requests: +25890 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27349 ___ Python tracker ___ _

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-24 Thread Terry J. Reedy
Terry J. Reedy added the comment: Yes, ask me to review. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-24 Thread Steven Hsu
Steven Hsu added the comment: Applying above suggestions, the first sentence of the entry "__future__" would be replaced by: A :ref:`future statement `, "from __future__ import *feature* ...", directs the compiler to compile the current module using syntax or semantics that will become stan

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-23 Thread Terry J. Reedy
Terry J. Reedy 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

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-23 Thread Steven D'Aprano
Steven D'Aprano added the comment: What exactly is a "pseudo-module"? I can only imagine it is something like sys, which exists internally in the interpreter but doesn't have an independent existence as a .py .dll or .so file. That's not the case with `__future__`, which is an *actual* modul

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-23 Thread Terry J. Reedy
Terry J. Reedy added the comment: I thnk the glossary should say both. Approximately: "When the first statement of a program starts 'from __future__ import feature', a pseudo-module ... . When used later in a program, __future__ is a real module." Link each statement to an appropriate pla

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-23 Thread Éric Araujo
Éric Araujo added the comment: > it doesn't do a normal import of the `__future__.py` module, it is actually a > compiler directive. It’s both! The compiler has special handling for this line (pseudo-module), and the interpreter does a regular import that gets the regular python module whic

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-21 Thread Steven Hsu
Steven Hsu added the comment: It sounds like that both descriptions (pseudo- and real) are true in different points of view on the __future__ module. I have no idea how to resolve this contradiction of the original design of the module. Any suggestion? Thanks for reply. -- ___

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-21 Thread Steven D'Aprano
Steven D'Aprano added the comment: I agree that the contradiction should be resolved. There is an actual `__future__.py` module, which on my system it is at /usr/local/lib/python3.9/__future__.py But when we use the special syntax: from __future__ import it doesn't do a normal import

[issue44693] Unclear definition of the "__future__" module in Docs

2021-07-21 Thread Steven Hsu
New submission from Steven Hsu : In Doc/glossary.rst, the first sentence of the entry "__future__" is that "A pseudo-module which programmers can use to enable new language features which are not compatible with the current interpreter." However, in Doc/library/__future__.rst, the first sente