[Python-Dev] Revert #12085 fix for __del__ attribute error message
ncoghlan at gmail.com
Thu Sep 26 06:59:17 CEST 2013
On 26 September 2013 09:05, Cameron Simpson <cs at zip.com.au> wrote:
> On 24Sep2013 09:33, Glenn Linderman <v+python at g.nevcal.com> wrote:
> | [MRAB]:
> | >> Why not just say something like "Cannot propagate exception..."; it's
> | >> simpler than "Unpropagatable exception...". [...]
> | First one I've heard that accurately and unambiguously and briefly
> | describes the issue.
> | +1
> I'm strongly in favour of Georg's one ("Exception in __del__ caught and not propagated").
> It says simply and clearly what has happened.
> It denotes the relevant context (__del__) in which it happened.
> The reader can then decide to find out why that decision may have been made.
Such a change is highly unlikely to happen, as it would require
changing every location where we call PyErr_WriteUnraisable.
> Why not MRAB's? ("Cannot propagate exception...")
> While better than "Unpropagatable exception" and "unraisable" and
> "unreraisable", it has the same flaw that I think underlies Antoine's
> concerns: it suggests the reason there's an error printed instead
> of further propagation is a _property of the exception_.
> It doesn't say it outright, but as an outsider that is definitely
> what I would at first infer.
It's substantially better than the status quo, though, and it
shouldn't require any changes outside PyErr_WriteUnraisable.
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the Python-Dev