26 Jul
2011
26 Jul
'11
11:47 a.m.
Glenn Linderman writes:
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.
Eh, doesn't it bother anybody that it's not an error, but a user action? If it needs a separate name, something like InterruptException seems most accurate to me.