➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: input() vs __future__
Type: Stage:
Components: Interpreter Core Versions: Python 2.4
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: hyeshik.chang Nosy List: hyeshik.chang, mwh
Priority: normal Keywords: patch

Created on 2004-01-13 16:17 by mwh, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
input-future.diff mwh, 2004-01-13 16:17 mwh's fix #1
inputfuture-test.diff hyeshik.chang, 2004-02-01 05:46 perky's unittest #1
Messages (4)
msg45277 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2004-01-13 16:17 
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.
msg45278 - (view) Author: Hyeshik Chang (hyeshik.chang) * (Python committer) Date: 2004-02-01 05:46 
Logged In: YES 
user_id=55188

I wrote a unittest. How's this?
msg45279 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2004-02-02 11:00 
Logged In: YES 
user_id=6656

Looks fine to me.  Check it in.
msg45280 - (view) Author: Hyeshik Chang (hyeshik.chang) * (Python committer) Date: 2004-02-02 13:43 
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
History
Date User Action Args
2022-04-11 14:56:02adminsetgithub: 39812
2004-01-13 16:17:35mwhcreate