Due to the nature of Python exceptions this indeed can only ever be a
heuristic. Some Python errors are already very specific, and we *don't*
want their message be part of the signature. For example, we want to
treat PermissionError('/home/fred/foo') and
PermissionError('/home/joe/bar') as one and
We should also dissect OSErrors and append errno. Python 3 already does
that by having specific subclasses such as PermissionError for EACCES,
but this is still useful for Python 2 or if we run into an errno which
doesn't have a subclass.
** Changed in: apport (Ubuntu)
Assignee: (unassigned)
2 matches
Mail list logo
