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 mbrierst
Recipients BreamoreBoy, ajaksu2, georg.brandl, mbrierst, ysj.ray
Date 2010-08-19.01:07:21
SpamBayes Score 4.73545e-11
Marked as misclassified No
Message-id <>
Wow, you wait 3/4 of a decade or so and the status of these bugs does tend to change on you.  I'm not sure it's fixed, but it is different.  Here's a test script for you:

import readline
import signal
def handle(a,b):
   print "received signal"
signal.signal(signal.SIGALRM, handle)
name = raw_input('Please enter your name within 5 seconds: ')
print name

The behavior of this script as is, since at least python 2.5 or so, is after 5 seconds to run the signal handler and then keep waiting for input (assuming you've got readline on your box of course).  I like this behavior, everything seems good to me so far.

Now comment out the "import readline", and suddenly you're getting an EOFError after the signal handler runs normally.  Still better than it used to be in 2003, but I'm not sure if this inconsistency is okay or not.

Now let's throw another wrench in the system.  Raise an exception in the signal handler.  Suddenly both are consistent again with and without readline, both raising the exception from the signal handler.  Sounds good to me.

So I guess someone has to decide, is this EOFError a new bug?  Or is this inconsistency acceptable and/or too hard to fix?  I haven't looked at the code in forever, so I can't speak for how hard it would be to fix.
Date User Action Args
2010-08-19 01:07:25mbrierstsetrecipients: + mbrierst, georg.brandl, ajaksu2, ysj.ray, BreamoreBoy
2010-08-19 01:07:25mbrierstsetmessageid: <>
2010-08-19 01:07:23mbrierstlinkissue706406 messages
2010-08-19 01:07:21mbrierstcreate