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 giampaolo.rodola
Recipients giampaolo.rodola, josh.r, rosslagerwall
Date 2019-04-05.18:44:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1554489845.25.0.336875274229.issue36488@roundup.psfhosted.org>
In-reply-to
Content
sendfile() on BSD/OSX is complicated by the headers/trailers args. You'll have to take that into account in the retry logic, adding unnecessary complexity. Since sendfile() may already return fewer bytes than requested (e.g. non-blocking sockets or big files) it's just easier to return the bytes sent thus far (if any). I can work on a patch once I find some time.

> Wasn't the point of PEP475 that all EINTR returns would be explicitly handled by retrying rather than forcing the user to handle it?

From PEP475: <<[...] to relieve application code from the burden of doing so>>
History
Date User Action Args
2019-04-05 18:44:05giampaolo.rodolasetrecipients: + giampaolo.rodola, rosslagerwall, josh.r
2019-04-05 18:44:05giampaolo.rodolasetmessageid: <1554489845.25.0.336875274229.issue36488@roundup.psfhosted.org>
2019-04-05 18:44:05giampaolo.rodolalinkissue36488 messages
2019-04-05 18:44:05giampaolo.rodolacreate