#18545: Improve the error message when the implicit settings configuration fails
-------------------------------+------------------------------------
Reporter: ncoghlan | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by anonymous):
Russell Keith-Magee and I were able to discuss this briefly at PyConAU.
For the second part, it may be worth pursuing that as a general
improvement to LazyObject. The trick is to avoid losing existing debugging
data in the Python 2 case - in Python 3, it would be possible to just do
"raise X from Y" when the init call fails to add the extra info about
which attribute was being looked up without losing the original traceback,
but in Python 2, raising a new exception means losing the original
traceback. Perhaps it would be enough to just preserve the original error
message? Is gaining the attribute name worth losing the inner part of the
traceback?
The first part should be relatively straightforward, though - that's just
a matter of mentioning the direct API in the error message.
(I ended up keeping busy with CPython at the sprints though, so I
unfortunately never followed it up at the sprints).
--
Ticket URL: <https://code.djangoproject.com/ticket/18545#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
