exception name is relative, not absolute - can be ambiguous
Bug #856273 reported by
James Henstridge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OOPS model |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Currently we set report['type'] to the exception's __name__. It'd be nice if we included the full module path of the exception to help distinguish exceptions with identical short names (i.e. which "DatabaseError" is this report referring to?).
My preference would be to just include the full path in the 'type' field of the report, but if that is going to cause compatibility issues, I guess it could be stored in a separate field.
| Changed in python-oops: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 856273] Re: include full exception name in reports | #1 |
| summary: |
- include full exception name in reports + exception name is relative, not absolute - can be ambiguous |
| Changed in python-oops: | |
| importance: | High → Low |
To post a comment you must log in.
Thats a good idea. I think there are two compatibility issues:
- oops tools aggregation won't aggregate an old/new together, and any
filtering done on type will need to be updated
- tests that look for the simple name will be need updating.
Both are shallow, so lets JFDI it.