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 eric.smith
Recipients YoSTEALTH, eric.smith
Date 2020-02-18.13:03:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582030986.37.0.502233671606.issue39673@roundup.psfhosted.org>
In-reply-to
Content
> These are both timeout errors but only `ETIMEDOUT` is accounted for?

Yes, only ETIMEDOUT is accounted for in Objects/exceptions.c. There's precedent for mapping multiple errnos to the same exception:

    ADD_ERRNO(BlockingIOError, EAGAIN);
    ADD_ERRNO(BlockingIOError, EALREADY);
    ADD_ERRNO(BlockingIOError, EINPROGRESS);
    ADD_ERRNO(BlockingIOError, EWOULDBLOCK);

You should probably raise this on python-ideas. I don't know if ETIME has some other accepted meaning. It's not mapped to any other exception, so it could be easily added. The only thing it would affect are people who are catching OSError and TimeoutError and are expecting ETIME to give an OSError, which seems a pretty niche case. Or I guess people who only catch TimeoutError and want to not catch the case where errno==ETIME.
History
Date User Action Args
2020-02-18 13:03:06eric.smithsetrecipients: + eric.smith, YoSTEALTH
2020-02-18 13:03:06eric.smithsetmessageid: <1582030986.37.0.502233671606.issue39673@roundup.psfhosted.org>
2020-02-18 13:03:06eric.smithlinkissue39673 messages
2020-02-18 13:03:06eric.smithcreate