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 Joseph Sible
Recipients Joseph Sible, benjamin.peterson, miss-islington
Date 2018-09-12.23:03:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536793415.61.0.956365154283.issue34004@psf.upfronthosting.co.za>
In-reply-to
Content
Re musl changing their behavior, see https://www.openwall.com/lists/musl/2018/09/07/1 and the resulting thread.

In addition to the old kernel version issue, two other issues were raised:
1. EINTR makes programming mistakes more likely, as people won't think to handle it. I don't give much weight to this point.
2. Most of the time, counting on receiving an EINTR results in race conditions. Our code seems to be affected by this too. Even on glibc, a signal at just the "right" time could result in it not being interrupted. This is why I think moving to an eventfd or something would be better, since we could then use pselect/ppoll/etc. to avoid the signal blocking race.
History
Date User Action Args
2018-09-12 23:03:35Joseph Siblesetrecipients: + Joseph Sible, benjamin.peterson, miss-islington
2018-09-12 23:03:35Joseph Siblesetmessageid: <1536793415.61.0.956365154283.issue34004@psf.upfronthosting.co.za>
2018-09-12 23:03:35Joseph Siblelinkissue34004 messages
2018-09-12 23:03:35Joseph Siblecreate