#16245: send_robust should include traceback in response when Exception occurs --------------------------------------+------------------------------------ Reporter: jsdalton | Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Other) | Version: SVN Severity: Normal | Resolution: Keywords: signals | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 --------------------------------------+------------------------------------
Comment (by development@…): Replying to [comment:1 jsdalton]: > In researching this patch I also learned that all this is unnecessary in Python 3.0. Per PEP 3134 (http://www.python.org/dev/peps/pep-3134/), Exception objects in Python 3.0 have a __traceback__ attribute which hold the traceback object for the call stack at the point where the exception occurred. If traceback is an attribute of the exception in python 3.0, then why don't we emulate that here? Add the traceback as an attribute of the returned exception. Either way, I hope this is able to get into 1.4. Its definitely needed. -- Ticket URL: <https://code.djangoproject.com/ticket/16245#comment:13> 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.