Hello,
just one more question:
Well, yes, you should, but still keep in mind that you can actually just
pass the request like so:
.addErrback(handleErrors, request)
You don't really have to save the request itself anywhere as an attribute.
if I understand correctly, when I put this
Maciej Wasilak wasi...@gmail.com wrote:
Hello,
just one more question:
Well, yes, you should, but still keep in mind that you can actually
just
pass the request like so:
.addErrback(handleErrors, request)
You don't really have to save the request itself anywhere as an
attribute.
if I
Laurens,
You don't have to do it from in there. You can do
.addErrback(handleErrors, request), since it's all the same request object,
right?
Aaargh! I see the problem now. I wrote everything as part of the Protocol
class (DD - DeferredsDictionaries), when I should have extracted request
On Thu, Sep 5, 2013 at 12:00 PM, Maciej Wasilak wasi...@gmail.com wrote:
Laurens,
You don't have to do it from in there. You can do
.addErrback(handleErrors, request), since it's all the same request object,
right?
Aaargh! I see the problem now. I wrote everything as part of the
Cześć Maciek :)
In general, you can pass extra arguments when you call addCallback(s) or
addErrback. They will get passed to the callback.
However, as a side note to that code example, do you understand the
difference between
.addCallbacks(cb, eb)
and:
.addCallback(cb).addErrback(eb)
and:
