[Python-Dev] Revert #12085 fix for del attribute error message (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Tue Sep 24 09:29:59 CEST 2013

On 24 September 2013 10:50, Stephen J. Turnbull <stephen at xemacs.org> wrote:

MRAB writes:

> > The word doesn't literally mean the exception itself was unraisable. It > > means it was raised, we caught it and we're writing it to stderr because > > we can't raise it again. > Ah, you mean "unreraisable". :-) +1 Ugly as sin, but satisfies all other criteria (except for Antoine's "easily understandable" which simply can't be satisfied).

If you're drawing a distinction between the first time an exception hits the eval loop and the second and subsequent times, then neither "Unraisable" nor "Unreraisable" is 100% correct. I just think it's a meaningless distinction, which is why I favour "Unraisable" - at the point in time where that message is displayed, that exception cannot be raised any further, whether it was created directly from C or was received from an underlying call back into Python code..

Cheers, Nick.

-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia

More information about the Python-Dev mailing list