On Feb 18, 10:23 am, Jean-Paul Calderone
wrote:
> The exception is caused by a syscall returning EINTR. A syscall will
> return EINTR when a signal arrives and interrupts whatever that
> syscall
> was trying to do. Typically a signal won't interrupt the syscall
> unless you've installed a signal
On Feb 17, 8:46 pm, Philip Winston wrote:
> We have a multiprocess Python program that uses Queue to communicate
> between processes. Recently we've seen some errors while blocked
> waiting on Queue.get:
>
> IOError: [Errno 4] Interrupted system call
>
> What causes the exception? Is it necessar
In article
,
Philip Winston wrote:
> We have a multiprocess Python program that uses Queue to communicate
> between processes. Recently we've seen some errors while blocked
> waiting on Queue.get:
>
> IOError: [Errno 4] Interrupted system call
>
> What causes the exception?
Unix divides sys
On Thu, Feb 17, 2011 at 5:46 PM, Philip Winston wrote:
> We have a multiprocess Python program that uses Queue to communicate
> between processes. Recently we've seen some errors while blocked
> waiting on Queue.get:
>
> IOError: [Errno 4] Interrupted system call
>
> What causes the exception?
On Fri, Feb 18, 2011 at 11:46 AM, Philip Winston wrote:
> We have a multiprocess Python program that uses Queue to communicate
> between processes. Recently we've seen some errors while blocked
> waiting on Queue.get:
>
> IOError: [Errno 4] Interrupted system call
>
> What causes the exception?
We have a multiprocess Python program that uses Queue to communicate
between processes. Recently we've seen some errors while blocked
waiting on Queue.get:
IOError: [Errno 4] Interrupted system call
What causes the exception? Is it necessary to catch this exception
and manually retry the Queue
