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

R. David Murray rdmurray at bitdance.com
Mon Sep 23 18:23:55 CEST 2013

On Mon, 23 Sep 2013 17:22:45 +0200, Antoine Pitrou <solipsis at pitrou.net> wrote:

On Mon, 23 Sep 2013 18:51:04 +1000 Nick Coghlan <ncoghlan at gmail.com> wrote: > On 23 September 2013 18:45, Antoine Pitrou <solipsis at pitrou.net> wrote: > > Le Mon, 23 Sep 2013 18:17:51 +1000, > > Nick Coghlan <ncoghlan at gmail.com> a écrit : > >> > >> Here's what I suggest changing that error to: > >> > >> >>> del x > >> Unraisable exception suppressed when calling >> of <_main_.C object at 0x7f98b8b61538>> > >> Traceback (most recent call last): > >> File "", line 3, in del > >> RuntimeError: Going away now > > > > Why not simply "Exception automatically caught in > C.del> [...]" ? > > It only answers the "what" (i.e. the exception was automatically > caught), without addressing the "why" (i.e. because there wasn't > anything else useful the interpreter could do with it)

Yes, but I agree with Greg that "unraisable" is wrong. After all, it was raised, and it can even be caught by the programmer (inside del).

Would it work to say "Asynchronous exception suppressed..."? It's not-entirely-precise, but it's less imprecise than "unraisable".

--David

More information about the Python-Dev mailing list