input() vs __future__

[mwhudson]

BPO	876178
Nosy	@mwhudson, @hyeshik
Files	input-future.diff: mwh's fix Support "bpo-" in Misc/NEWS #1 inputfuture-test.diff: perky's unittest Support "bpo-" in Misc/NEWS #1

^{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/hyeshik'
closed_at = <Date 2004-02-02.13:43:20.000>
created_at = <Date 2004-01-13.16:17:35.000>
labels = ['interpreter-core']
title = 'input() vs __future__'
updated_at = <Date 2004-02-02.13:43:20.000>
user = 'https://github.com/mwhudson'

bugs.python.org fields:

activity = <Date 2004-02-02.13:43:20.000>
actor = 'hyeshik.chang'
assignee = 'hyeshik.chang'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2004-01-13.16:17:35.000>
creator = 'mwh'
dependencies = []
files = ['5785', '5786']
hgrepos = []
issue_num = 876178
keywords = ['patch']
message_count = 4.0
messages = ['45277', '45278', '45279', '45280']
nosy_count = 2.0
nosy_names = ['mwh', 'hyeshik.chang']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue876178'
versions = ['Python 2.4']

[mwhudson]

There's a thread on comp.lang.python about input()s
lack of interaction with __future__ statements:

>>> from __future__ import division
>>> input('blah: ')
blah: 1/2
0

This simple patch fixes that. Not sure how to write a
testcase, though.

[hyeshik]

Logged In: YES
user_id=55188

I wrote a unittest. How's this?

[mwhudson]

Logged In: YES
user_id=6656

Looks fine to me. Check it in.

[hyeshik]

Logged In: YES
user_id=55188

Ok. Checked in:
Misc/NEWS 1.926
Python/bltinmodule.c 2.308
Lib/test/test_builtin.py 1.28