> in your patch, I think we need to check the return code of
> PyErr_CheckSignals and return - or will pyrex automatically take care
> of that if an exception is raised?
Pyrex will take care of that, that's what the 'except -1' in the import
declaration for PyErr_CheckSignals does.
> It looks like we actually need similar handling in every case where
> this code is turning errno into an OSError or similar.
Yeah. Or at least for every case where errno might be EINTR or
otherwise caused by the arrival of a signal... I'm not sure if there are
any?. A common function sounds like a good idea.
> in your patch, I think we need to check the return code of
> PyErr_CheckSignals and return - or will pyrex automatically take care
> of that if an exception is raised?
Pyrex will take care of that, that's what the 'except -1' in the import
declaration for PyErr_CheckSignals does.
> It looks like we actually need similar handling in every case where
> this code is turning errno into an OSError or similar.
Yeah. Or at least for every case where errno might be EINTR or
otherwise caused by the arrival of a signal... I'm not sure if there are
any?. A common function sounds like a good idea.