[Python-Dev] Re: Map errno==ETIME to TimeoutError

2020-05-26 Thread Giampaolo Rodola'
Sigh! I misread this discussion and thought the proposal was to add
TimeoutError which I forgot existed. Sorry for the noise and please
disregard my previous message.

On Mon, May 25, 2020 at 4:32 PM Giampaolo Rodola' 
wrote:

> 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  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) 
>>  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
>
>

-- 
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/BRVOG53QLBOM727IMOXBE7C7HEWYOBHI/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: Map errno==ETIME to TimeoutError

2020-05-26 Thread Antoine Pitrou
On Mon, 25 May 2020 04:38:17 -0400
"Eric V. Smith"  wrote:
> On 5/25/2020 4:25 AM, Serhiy Storchaka wrote:
> > 24.05.20 17:48, Eric V. Smith пише:  
> >> 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 "STREAMioctl(2) 
> >>  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.  
> >
> > Why it was not mapped at first place? Was there any discussion?  
> 
> Good question. Perhaps Antoine can answer.
> 
> I don't see any mention of ETIME in PEP 3151. I'm assuming it was just 
> an oversight. I couldn't find any reference to ETIME on python-ideas or 
> python-dev (other than this discussion), either.

As Nathaniel said, it's simply because it didn't show up in any common
system calls.  It's probably harmless to add it, but probably also
mostly pointless :-)

Regards

Antoine.

___
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/CPBGSP4HHNH4F3HEO33QTTZJKHKVJN4S/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: Map errno==ETIME to TimeoutError

2020-05-26 Thread Barry


> On 24 May 2020, at 17:42, Eric V. Smith  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) 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.
> 

What kernel calls return this errno?
What is the current behaviour of thoses kernel calls?

Barry
> 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/
___
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/2HXW2ZE54CFDR6VEE7J7HPLDUNHEZCT4/
Code of Conduct: http://python.org/psf/codeofconduct/