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 tim.golden
Recipients Devin Jeanpierre, Dude-X, amaury.forgeotdarc, brian.curtin, christian.heimes, loewis, mhammond, pitrou, r.david.murray, ronaldoussoren, santoso.wijaya, tim.golden
Date 2012-06-27.13:04:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
OK, I've run out of time to look, but the culprit looks like it's an odd interaction between my_fgets in myreadline.c and the interrupt handler in signal. There's a section of code which is conditional on ERROR_OPERATION_ABORTED being returned from fgets in the CRT. 

That then tries to play ball with a the interrupt handler having fired already (in a separate thread) by sleeping for one second and checking that the handler was tripped. If it has then the function returns one and stuff happens elsewhere; it it hasn't then the function behaves as if EOF (ie Ctrl-Z) was pressed and Python exits.

That's as far as I've got; it looks like a race condition of some sort but I can't see where. I'm not 100% sure that the SIGINT handler is tripping.
Date User Action Args
2012-06-27 13:04:06tim.goldensetrecipients: + tim.golden, loewis, mhammond, ronaldoussoren, amaury.forgeotdarc, pitrou, christian.heimes, Dude-X, Devin Jeanpierre, r.david.murray, brian.curtin, santoso.wijaya
2012-06-27 13:04:06tim.goldensetmessageid: <>
2012-06-27 13:04:05tim.goldenlinkissue1677 messages
2012-06-27 13:04:05tim.goldencreate