➜

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 quark
Recipients Don Hatch, Finkregh, benjamin.peterson, dankegel, doko, draghuram, eric.araujo, ggenellina, jary, marhar, mjpieters, nvetoshkin, quark, r_mosaic, ralph.corderoy, vstinner
Date 2016-11-15.16:31:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479227520.06.0.0527564888381.issue1633941@psf.upfronthosting.co.za>
In-reply-to
Content 
haypo: The file.__iter__ EINTR issue may be better discussed as a separate bug report. It's not related to stdin or EOF or Windows.

Since we have some EINTR fixes for Python 2.7.4, I think it's reasonable to fix the remaining EINTR issues for 2.7.13+.

If I have read fileobject.c correctly, readahead() is the only remaining place having the EINTR issue.

If you agree that we should fix readahead(), I can prepare the patch.
History
Date User Action Args
2016-11-15 16:32:00quarksetrecipients: + quark, doko, mjpieters, ggenellina, vstinner, draghuram, marhar, r_mosaic, benjamin.peterson, eric.araujo, ralph.corderoy, nvetoshkin, Finkregh, jary, dankegel, Don Hatch
2016-11-15 16:32:00quarksetmessageid: <1479227520.06.0.0527564888381.issue1633941@psf.upfronthosting.co.za>
2016-11-15 16:32:00quarklinkissue1633941 messages
2016-11-15 16:31:59quarkcreate