Should __future__ print_function be valid in 3.0?

[ericvsmith]

BPO	2436
Nosy	@ericvsmith, @tiran

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/ericvsmith'
closed_at = <Date 2008-03-20.23:02:59.901>
created_at = <Date 2008-03-20.19:08:18.837>
labels = ['interpreter-core']
title = 'Should __future__ print_function be valid in 3.0?'
updated_at = <Date 2008-03-20.23:02:59.900>
user = 'https://github.com/ericvsmith'

bugs.python.org fields:

activity = <Date 2008-03-20.23:02:59.900>
actor = 'eric.smith'
assignee = 'eric.smith'
closed = True
closed_date = <Date 2008-03-20.23:02:59.901>
closer = 'eric.smith'
components = ['Interpreter Core']
creation = <Date 2008-03-20.19:08:18.837>
creator = 'eric.smith'
dependencies = []
files = []
hgrepos = []
issue_num = 2436
keywords = []
message_count = 3.0
messages = ['64193', '64195', '64221']
nosy_count = 2.0
nosy_names = ['eric.smith', 'christian.heimes']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue2436'
versions = ['Python 3.0']

[ericvsmith]

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.

[tiran]

Yes, you *must* implement it. From
http://docs.python.org/lib/module-future.html

No feature description will ever be deleted from __future__.

[ericvsmith]

Implemented in r61682.