I'm -1 because the concept of "timeout" is generic enough to be often implemented as a custom exception, which poses questions re. backward/forward compatibilty. E.g. in psutil I have "TimeoutExpired", also providing a "seconds" attribute. Also I've probably never seen ETIME / ETIMEDOUT happening, whereas AFAIU the point PEP 3151 was to create mappings for the most common errnos.
On Sun, May 24, 2020 at 6:48 PM Eric V. Smith <[email protected]> wrote: > Does anyone have an opinion on https://bugs.python.org/issue39673? It > maps ETIME to TimeoutError, in addition to the already existing ETIMEDOUT. > > http://man7.org/linux/man-pages/man3/errno.3.html says: > > *ETIME *Timer expired (POSIX.1 (XSI STREAMS option)). > > (POSIX.1 says "STREAM ioctl(2) > <http://man7.org/linux/man-pages/man2/ioctl.2.html> timeout".) > > *ETIMEDOUT *Connection timed out (POSIX.1-2001). > > > It seems like a reasonable change to me, but I'm not a subject matter > expert on STREAMS, or what other affect this might have. > > And if added to 3.10, should it be backported? I'd tend to say "no", > because of unknown impacts on existing code. > > Eric > > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/C7KK6VSGPQKPA5IUCZ2MHH7QNLP2Q5QX/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- Giampaolo - http://grodola.blogspot.com
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/B4Y2UZ3Z7ARHVP5JTP27UV2OH2PSDZ4P/ Code of Conduct: http://python.org/psf/codeofconduct/
