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 <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__). Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4