Terry J. Reedy added the comment:
The only currently active __future__ import is 'annotations'.
https://docs.python.org/3/reference/compound_stmts.html#index-23
The is currently scheduled to be needed indefinitely (until '4.0').
--
versions: +Python 3.10 -Python 3.6, Python 3.7
__
Terry J. Reedy added the comment:
I am no longer patching 2.7 but there is one __future__ import active in 3.6:
generator_stop. If I remember right, there is code that would work without
future import and fail with it. In 3.7, it would always fail.
--
assignee: -> terry.reedy
versio
Terry J. Reedy added the comment:
I agree that this is broken. I verified that the following works in 2.7.9
>>> from __future__ import division, print_function
>>> 32 / 5
6.4
>>> print(2,3,sep='**')
2**3
#13296 was about self.compile.compiler.flags (in ModifiedInterpreter, which
inherits .com
New submission from Raymond Hettinger:
Future imports in a module aren't transferring to the interactive shell when
executing Run Module.
Given the file tmp_future.py
$ cat tmp_future.py
from __future__ import division, print_function
print(32 / 5)
Run Python inte
