On 24 September 2013 10:50, Stephen J. Turnbull <step...@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 | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
