> I wouldn't go telling you to do more work than you think is
> necessary, but if you're willing to do eithr, I'd prefer to see the
> second solution in Django; for all the reasons you gave, plus it is
> "more backward compatible": Assume I have some code doing
>
> for receiver, response in m
On Wednesday 30 October 2013 11:23:07 unai wrote:
>
> Now, this ticket doubts between two possible solutions. The first of them
> is returning a `(receiver, (type, exception, traceback))` made by
> `(receiver, sys.exc_info())` tuple if `exc_info` is True:
>
> for receiver, (typ, exc, tbk) in
Hi everybody!
I'm trying to defrost the ticket #16245 that says that
`django.dispatch.dispatcher.Signal.send_robust` should include not only the
exception but also the traceback if something goes wrong.
At this moment, `send_robust` returns a list of (receiver, exception) tuples so
that...
f
