[Patches] [ python-Patches-876178 ] input() vs __future__
SourceForge.net
noreply at sourceforge.net
Sun Feb 1 00:46:19 EST 2004
Patches item #876178, was opened at 2004-01-14 01:17
Message generated for change (Comment added) made by perky
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=876178&group_id=5470
Category: Core (C code)
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Hudson (mwh)
Assigned to: Nobody/Anonymous (nobody)
Summary: input() vs __future__
Initial Comment:
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.
----------------------------------------------------------------------
>Comment By: Hye-Shik Chang (perky)
Date: 2004-02-01 14:46
Message:
Logged In: YES
user_id=55188
I wrote a unittest. How's this?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=876178&group_id=5470
More information about the Patches
mailing list