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.

Author Drekin
Recipients Drekin, tim.golden
Date 2013-08-25.11:43:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377431005.7.0.162590773424.issue18597@psf.upfronthosting.co.za>
In-reply-to
Content
Why are there actually more codepaths which may raise this issue? My naive idea would be that input() is just thin wrapper around sys.stdout.write() (for prompt) and sys.stdin.readline() which leads to sys.stdin.buffer.raw.read* where is the place where some low level OS-dependent function to actually get input from user is called (unistd.read or GNU readline or whatever). And also there is the place where the waiting for KeyboardInterrupt on Windows should occur.
History
Date User Action Args
2013-08-25 11:43:25Drekinsetrecipients: + Drekin, tim.golden
2013-08-25 11:43:25Drekinsetmessageid: <1377431005.7.0.162590773424.issue18597@psf.upfronthosting.co.za>
2013-08-25 11:43:25Drekinlinkissue18597 messages
2013-08-25 11:43:25Drekincreate