#862 closed defect (wontfix)
Which field caused method_save to bomb out?
| Reported by: | garthk | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | Metasystem | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If method_save fails whilst trying to call pre_save on a field, it can be tricky to figure out which field caused the problem without wading to exactly the right place in the stack frame or riddling meta\init.py with debugging code. To save everyone the effort, I've got a patch that'll append a descriptive message to the exception's arguments so the errant field name is obvious and easy to find from the last line of the traceback.
Attachments (1)
Change History (2)
by , 19 years ago
comment:1 by , 18 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Fix