#16245: send_robust should include traceback in response when Exception occurs
-------------------------------------+-------------------------------------
Reporter: jsdalton | Owner: nobody
Type: | Status: new
Cleanup/optimization | Component: Core (Other)
Milestone: | Severity: Normal
Version: SVN | Keywords: signals
Resolution: | Has patch: 1
Triage Stage: Design | Needs tests: 0
decision needed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by jsdalton):
I have updated the patch to reflect my last comment. Adding the traceback
as a third item the tuple response is now an option via
`append_traceback`, the default for which is False.
Existing implementation of `send_robust()` will now work as is. To make
use of my proposed feature, you would need to set append_traceback to True
when calling `send_robust()`.
If anyone has any objections or concerns I'd like to hear them. Accessing
the traceback at the point an exception occurs in a receiver function is
currently not possible. This makes it difficult if not impossible to debug
if something goes wrong in one of the receiver functions.
--
Ticket URL: <https://code.djangoproject.com/ticket/16245#comment:7>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
