From ebb0279f4a7a7155c44c09506bbe5b1f9acc83a2 Mon Sep 17 00:00:00 2001 From: Unai Zalakain Date: Wed, 30 Oct 2013 12:11:04 +0100 Subject: Fixed #16245 -- Included traceback in send_robust()'s response Exceptions from the (receiver, exception) tuples returned by ``send_robust()`` now have always their traceback attached as their ``__traceback__`` argument. --- docs/releases/1.8.txt | 4 +++- docs/topics/signals.txt | 5 +++++ 2 files changed, 8 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index aa39fb2b7c..94a4f3ed74 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -153,7 +153,9 @@ Models Signals ^^^^^^^ -* ... +* Exceptions from the ``(receiver, exception)`` tuples returned by + :meth:`Signal.send_robust() ` now have + their traceback attached as a ``__traceback__`` attribute. Templates ^^^^^^^^^ diff --git a/docs/topics/signals.txt b/docs/topics/signals.txt index 346d47d179..fb83258c9b 100644 --- a/docs/topics/signals.txt +++ b/docs/topics/signals.txt @@ -274,6 +274,11 @@ be notified of a signal in the face of an error. and ensures all receivers are notified of the signal. If an error occurs, the error instance is returned in the tuple pair for the receiver that raised the error. +.. versionadded:: 1.8 + + The tracebacks are present on the ``__traceback__`` attribute + of the errors returned when calling ``send_robust()``. + Disconnecting signals ===================== -- cgit v1.3