Showing content from http://mail.python.org/pipermail/python-dev/attachments/20130923/651f5019/attachment.html below:
<p dir="ltr"><br>
On 23 Sep 2013 06:38, "Terry Reedy" <<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a>> wrote:<br>
><br>
> On 9/22/2013 2:41 PM, Guido van Rossum wrote:<br>
>><br>
>> On Sun, Sep 22, 2013 at 10:35 AM, Terry Reedy <<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a><br>
>> <mailto:<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a>>> wrote:<br>
>><br>
>> On 9/21/2013 10:30 PM, Guido van Rossum wrote:<br>
>><br>
>> Exceptions in __del__ point to bugs (sometimes in the stdlib) that<br>
>> should be fixed, period. The only reason they do not result in<br>
>> exceptions that are properly bubbled up and catchable is because<br>
>> __del__<br>
>> is called from a DECREF macro which has no return value.<br>
>><br>
>><br>
>> That is clear enough. What fooled me is the word 'ignored', in both<br>
>> the doc and message. How about 'skipped' (for technical reasons)?<br>
>><br>
>><br>
>> That's a good point, although I'm not sure 'skipped' is better.<br>
><br>
><br>
> Only slightly ;-). The problem with both words is that they try to say two things. What happened, and what Python did about it.<br>
><br>
><br>
>> Maybe use a more neutral verb like 'occurred'?<br>
><br>
><br>
> "Exception occurred in ..." is even better at say what happened.<br>
><br>
> I think we should then add an explict statement as to what Python did, and hint at what the user should do, something like<br>
> "Although caught internally, it still indicates a problem."</p>
<p dir="ltr">Brevity is still a virtue. The relevant C API function is called "PyErr_WriteUnraisable", so just starting the message as something like "Unraisable exception suppressed in..." might work.</p>
<p dir="ltr">Cheers,<br>
Nick.</p>
<p dir="ltr">><br>
> Otherwise, when no other output follows, as in<br>
> ...<br>
> > del c<br>
> Exception ocurred in: <bound method C.__del__ ...<br>
><br>
> Traceback (most recent call last):<br>
> File "<pyshell#0>", line 2, in __del__<br>
> AttributeError:<br>
> >>><br>
> It may not be completely obvious to a non-expert that the traceback is not a 'real' traceback from an exception that was allowed to propagate, and that it did not stop execution and cannot be caught.<br>
><br>
><br>
> -- <br>
> Terry Jan Reedy<br>
><br>
> _______________________________________________<br>
> Python-Dev mailing list<br>
> <a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
> <a href="https://mail.python.org/mailman/listinfo/python-dev">https://mail.python.org/mailman/listinfo/python-dev</a><br>
> Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com">https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com</a><br>
</p>
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