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 neologix
Recipients felipecruz, neologix, pitrou, vstinner
Date 2012-10-03.18:19:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3GkrHn6S5HvnAfvuNdbf3XvR49PG2cnA7OaGVjyrSsyQ@mail.gmail.com>
In-reply-to <1349274197.16.0.980899350684.issue16105@psf.upfronthosting.co.za>
Content
>> Why limit to EBADF? You could also have EPIPE, EINVAL and many other errors.
>> The only error you may not want to report is EAGAIN.
>
> Charles,
> You're right! If all errno cases get covered in the patch,  will It looks reasonable?

Raising an error in case the signal can't be written to the FD
(because the other end didn't drain the pipe/socket) seems reasonable.
You should just retry on EINTR (although any sane implementation
shouldn't return EINTR on non-blocking write, I don't think it's
strictly prohibited by POSIX).
History
Date User Action Args
2012-10-03 18:19:19neologixsetrecipients: + neologix, pitrou, vstinner, felipecruz
2012-10-03 18:19:19neologixlinkissue16105 messages
2012-10-03 18:19:19neologixcreate