On 9/23/2013 12:23 PM, R. David Murray wrote:
On Mon, 23 Sep 2013 17:22:45 +0200, Antoine Pitrou <solip...@pitrou.net> wrote:
On Mon, 23 Sep 2013 18:51:04 +1000
Nick Coghlan <ncogh...@gmail.com> wrote:
On 23 September 2013 18:45, Antoine Pitrou <solip...@pitrou.net> wrote:
Le Mon, 23 Sep 2013 18:17:51 +1000,
Nick Coghlan <ncogh...@gmail.com> a écrit :
Here's what I suggest changing that error to:
del x
Unraisable exception suppressed when calling <bound method C.__del__
of <__main__.C object at 0x7f98b8b61538>>
Traceback (most recent call last):
File "<stdin>", line 3, in __del__
RuntimeError: Going away now
Why not simply "Exception automatically caught in <bound method
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,
As in the example above ('del x').
but it's less imprecise than "unraisable".
How 'troublesome'? That is always accurate, as proven by this thread.
We really need an "Understanding Exceptions" HOWTO, and I expect we will
get one. So I agree with Nick that something easily searched would be good.
--
Terry Jan Reedy
_______________________________________________
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
