> If WaitForSingleObjectEx fails, do you think the system error code should be raised as an OSError?

It's invalid (and unfixable) internal state, so perhaps SystemError makes the most sense? There's no point catching it in most cases.

Or since we don't want to worry too much about formatting the message, why not raise the OSError with the helper function and then immediately chain it with a fixed SystemError?