[issue2436] Should __future__ print_function be valid in 3.0?

[Eric Smith]

New submission from Eric Smith <eric at trueblade.com>:

Should this be accepted in 3.0, and become a no-op:
from __future__ import print_function
?

It might make using code in 2.6 and 3.0 easier, since you would not have
to delete this line.

I note that:
from __future__ import with_statement
is already valid in 3.0.

----------
assignee: eric.smith
components: Interpreter Core
messages: 64193
nosy: eric.smith
priority: normal
severity: normal
status: open
title: Should __future__ print_function be valid in 3.0?
versions: Python 3.0

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2436>
__________________________________