Part of twisted.internet.defer View Source View In Hierarchy
Known subclasses: twisted.internet.defer.DeferredList, twisted.persisted.crefutil._Defer
This is a callback which will be put off until later.
Why do we want this? Well, in cases where a function in a threaded
program would block until it gets a result, for Twisted it should not
block. Instead, it should return a Deferred
.
This can be implemented for protocols that run over the network by
writing an asynchronous protocol for twisted.internet
. For methods
that come from outside packages that are not under our control, we use
threads (see for example twisted.enterprise.adbapi
).
Method | __init__ | Undocumented |
Method | addCallbacks | Add a pair of callbacks (success and error) to this Deferred .
|
Method | addCallback | Convenience method for adding just a callback. |
Method | addErrback | Convenience method for adding just an errback. |
Method | addBoth | Convenience method for adding a single callable as both a callback |
Method | chainDeferred | Chain another Deferred to
this Deferred .
|
Method | callback | Run all success callbacks that have been added to this Deferred .
|
Method | errback | Run all error callbacks that have been added to this Deferred .
|
Method | pause | Stop processing on a Deferred until
unpause ()
is called.
|
Method | unpause | Process all callbacks made since pause ()
was called.
|
Method | setTimeout | Set a timeout function to be triggered if I am not called. |
Method | __str__ | Undocumented |
Method | _continue | Undocumented |
Method | _startRunCallbacks | Undocumented |
Method | _runCallbacks | Undocumented |
Add a pair of callbacks (success and error) to this Deferred
.
Convenience method for adding a single callable as both a callback and an errback.
SeeaddCallbacks
.
Chain another Deferred
to
this Deferred
.
Deferred
to
call d
's callback or errback, as appropriate. It is merely a
shorthand way of performing the following:
self.addCallbacks(d.callback, d.errback)When you chain a deferred d2 to another deferred d1 with d1.chainDeferred(d2), you are making d2 participate in the callback chain of d1. Thus any event that fires d1 will also fire d2. However, the converse is not true; if d2 is fired d1 will not be affected.
Run all success callbacks that have been added to this Deferred
.
Failure
or
raises an Exception
, processing will continue on the *error*-
callback chain.
Run all error callbacks that have been added to this Deferred
.
Each callback will have its result passed as the first argument to the
next; this way, the callbacks act as a 'processing chain'. Also, if the
error-callback returns a non-Failure or doesn't raise an
Exception
, processing will continue on the *success*-callback
chain.
If the argument that's passed to me is not a failure.Failure
instance, it will be embedded in one. If no argument is passed, a failure.Failure
instance will be created based on the current traceback stack.
Raises | NoCurrentExceptionError | If fail is None but there is no current
exception state.
|
Parameters | seconds | How long to wait (from now) before firing the
timeoutFunc .
|
timeoutFunc | will receive the Deferred and
*args, **kw as its arguments. The default timeoutFunc will
call the errback with a TimeoutError .
|