[issue22606] Inconsistency between Python 2 and PyPy regarding future imports

Benjamin Peterson added the comment: If you fully compiled this code, it would fail. CPython checks the well-formedness of __future__ statements after ast parsing. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python t

[issue22606] Inconsistency between Python 2 and PyPy regarding future imports

Batuhan added the comment: I guess this issue expired (due to python2). -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-l

[issue22606] Inconsistency between Python 2 and PyPy regarding future imports

Terry J. Reedy added the comment: A difference in internal behavior between CPython and PyPy is not necessarily a CPython bug, or even a PyPy bug. It may just be an implementation choice. So ignore PyPy and consider Python doc versus CPython behavior. Running the three quoted lines by themse

[issue22606] Inconsistency between Python 2 and PyPy regarding future imports

New submission from Claudiu Popa: Hi, The following code gives similar errors for both PyPy and Python 2 when called, but totally different AST objects. Given the following code, PyPy says that `print(4)` is an _ast.Print, while Python 2 believes that it is an _ast.Expr (which wraps a Call).