Re: [Python-Dev] PEP 475 accepted

2015-02-03 Thread Georg Brandl
On 02/03/2015 04:25 PM, Larry Hastings wrote: > > On 02/02/2015 12:58 PM, Victor Stinner wrote: >> 2015-02-02 21:49 GMT+01:00 Guido van Rossum : >>> W00t! Congratulations les Français! >> We will celebrate this acceptance with a glass of red wine and cheese. > > If it were me, I'd use separate gl

Re: [Python-Dev] PEP 475 accepted

2015-02-03 Thread Larry Hastings
On 02/02/2015 12:58 PM, Victor Stinner wrote: 2015-02-02 21:49 GMT+01:00 Guido van Rossum : W00t! Congratulations les Français! We will celebrate this acceptance with a glass of red wine and cheese. If it were me, I'd use separate glasses. //arry/ __

Re: [Python-Dev] PEP 475 accepted

2015-02-03 Thread Victor Stinner
2015-02-03 15:25 GMT+01:00 Giampaolo Rodola' : > OK, thanks for clarifying, this is a very nice addition. One last thing: > should InterruptedError exception be deprecated? As far as I understand it > should never occur again, right? signal.setinterrupt() is not deprecated so you can still "disabl

Re: [Python-Dev] PEP 475 accepted

2015-02-03 Thread Giampaolo Rodola'
On Mon, Feb 2, 2015 at 10:46 PM, Victor Stinner wrote: > 2015-02-02 22:11 GMT+01:00 Giampaolo Rodola' : > > I may be chiming in a little late, however, I'd have a question: does > this > > affect non-blocking applications somehow? > > How often should we expect to receive EINTR? > > Each time a p

Re: [Python-Dev] PEP 475 accepted

2015-02-03 Thread Nick Coghlan
On 3 Feb 2015 06:46, "Antoine Pitrou" wrote: > > > Hello, > > I'm now accepting PEP 475 - "Retry system calls failing with EINTR". > You can read it at https://www.python.org/dev/peps/pep-0475/ > > The implementation is more or less ready at > http://bugs.python.org/issue23285, so you can expect i

Re: [Python-Dev] PEP 475 accepted

2015-02-02 Thread Victor Stinner
2015-02-02 22:11 GMT+01:00 Giampaolo Rodola' : > I may be chiming in a little late, however, I'd have a question: does this > affect non-blocking applications somehow? > How often should we expect to receive EINTR? Each time a program is interrupted by a signal while it was waiting for a sycall. M

Re: [Python-Dev] PEP 475 accepted

2015-02-02 Thread Giampaolo Rodola'
On Mon, Feb 2, 2015 at 9:45 PM, Antoine Pitrou wrote: > > Hello, > > I'm now accepting PEP 475 - "Retry system calls failing with EINTR". > You can read it at https://www.python.org/dev/peps/pep-0475/ > > The implementation is more or less ready at > http://bugs.python.org/issue23285, so you can

Re: [Python-Dev] PEP 475 accepted

2015-02-02 Thread Antoine Pitrou
On Mon, 2 Feb 2015 12:49:32 -0800 Guido van Rossum wrote: > W00t! Congratulations les Français! I hoped nobody would notice :-) Regards Antoine. > > On Mon, Feb 2, 2015 at 12:45 PM, Antoine Pitrou wrote: > > > > > Hello, > > > > I'm now accepting PEP 475 - "Retry system calls failing with

Re: [Python-Dev] PEP 475 accepted

2015-02-02 Thread Victor Stinner
2015-02-02 21:49 GMT+01:00 Guido van Rossum : > W00t! Congratulations les Français! We will celebrate this acceptance with a glass of red wine and cheese. Thanks Antoine! I hate EINTR. It's a pain to handle them for each syscall in subprocess and asyncio (where signals are likely). It's good to n

Re: [Python-Dev] PEP 475 accepted

2015-02-02 Thread Guido van Rossum
W00t! Congratulations les Français! On Mon, Feb 2, 2015 at 12:45 PM, Antoine Pitrou wrote: > > Hello, > > I'm now accepting PEP 475 - "Retry system calls failing with EINTR". > You can read it at https://www.python.org/dev/peps/pep-0475/ > > The implementation is more or less ready at > http://b

[Python-Dev] PEP 475 accepted

2015-02-02 Thread Antoine Pitrou
Hello, I'm now accepting PEP 475 - "Retry system calls failing with EINTR". You can read it at https://www.python.org/dev/peps/pep-0475/ The implementation is more or less ready at http://bugs.python.org/issue23285, so you can expect it to land in the main repo relatively soon. Regards Antoine