#16245: send_robust should include traceback in response when Exception occurs
----------------------------------+------------------------------
Reporter: jsdalton | Owner: nobody
Type: Cleanup/optimization | Status: new
Milestone: 1.4 | Component: Core (Other)
Version: SVN | Severity: Normal
Keywords: signals | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------+------------------------------
I have cron job that runs a task which sends a signal via `send_robust`. I
ran into a wall recently in trying to configure better logging for this
job. The basic problem is that I can't access the traceback for any
exception that occurred in a receiver, which makes debugging in my
situation something of a nightmare.
As it stands now, if an exception occurs in a receiver when a
`send_robust` signal is sent, a tuple is added to the responses list which
contains the receiver function and the exception.
I would like to propose that we include the traceback as a third item in
the tuple. With the exception and traceback, it is possible to construct
the `(type, value, traceback)` returned by `sys.exc_info()` (and used by
the Python logging module), so that exceptions in receiver functions can
be more effectively debugged.
A patch will require no more than a line or two in production and test
code and probably a minor documentation tweak.
I will submit a patch for this shortly, unless anybody presents any
objections or concerns.
--
Ticket URL: <https://code.djangoproject.com/ticket/16245>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
