[Python-Dev] Comments of the PEP 3151 (original) (raw)

Stephen J. Turnbull stephen at xemacs.org
Tue Jul 26 05:47:01 CEST 2011

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.

More information about the Python-Dev mailing list