On 7/25/2011 3:43 AM, Antoine Pitrou wrote:
On Mon, 25 Jul 2011 15:28:47 +1000
Nick Coghlan<ncogh...@gmail.com> wrote:
>
> > If we add EINTR, I don't know if it's better to add it to
> > BlockingIOError or to create a new exception (InterruptError?).
>
> InterruptedError seems like a reasonable candidate for addition to me
> - catch and retry in that case is something developers are likely to
> want to do.
Ok, let's call it InterruptError then. InterruptedError sounds like the
error was interrupted;)
Sorry, no. "InterruptError" sounds too much like a CPU interrupt
signal, which the error is not. "InterruptedError" is OK by me, I don't
see the confusion you do. But maybe "InterruptedOperationError" would
be the most clear. Way too long, of course, so maybe
"InterruptedAPIError" or "InterruptedOpError" or "EINTRError" in my
order of preference.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
