Terry Jones writes:
> But, I also built some queuing things where I would have liked extra
> information. For example, an app is processing jobs on behalf of a user,
> [...]
Thinking about this for a little bit, it seems like there is quite a bit
more state to your jobs, that simply an eventual r
Terry Jones writes:
> OK, maybe someone can explain the original "Well, it already raises
> `CancelledError`. Every deferred that doesn't have explicitly handle
> cancelling already does:" to me, because I didn't get it at all!
This is what happens when a deferred is cancelled:
a) If the deferre
On 18 Jun, 08:58 pm, ter...@gmail.com wrote:
From the practical POV the most welcomed first step in updating the
Twisted
log system would be introduction of ready made log levels (with an
ability
to filter on them in observers), fix of logPrefix thing and somewhat
extended set of available obse
By the way, I don't need any of this to make its way into Twisted. I can
still write my own class that does what I want (well, wanted). Below is a
2013 version of the CancelableDeferred. It's untested. The basic idea is
that if you get a regular deferred from somewhere, you can use the class
belo
Hi JP
> This is not to say that I believe there is no application that might want
this information, but maybe someone can
> propose some concrete use cases for this information and design can
follow from that. So far I don't think any
> practical justification to do anything other than `Cancelled
> Thank you for pointing this out. It seems like an important fact that
makes the rest of the discussion moot.
OK, maybe someone can explain the original "Well, it already raises
`CancelledError`. Every deferred that doesn't have explicitly handle
cancelling already does:" to me, because I didn't
On 19 Jun, 07:49 pm, tom.pri...@ualberta.net wrote:
Well, it already raises `CancelledError`. Every deferred that doesn't
have explicitly handle cancelling already does:
from twisted.mail import smtp
from twisted.python import log
d = smtp.sendmail("host", "options.sender", [], "")
d.cancel()
My original plan, as suggested by exarkun, is to start with something easy
to implement like netstring and then move on to advanced ones. But after
today's video chat with tom and dash, I will begin by rewriting the
Message.decode/encode part inside names.dns. The expected outcome, I think,
is to t
On 20 June 2013 04:04, Christopher Armstrong wrote:
> Hi Shiyao, I'm happy that you chose Twisted as your SoC project. I just want
> to point out that Richard Wall (rwall on IRC) has been working a lot on DNS
> lately, he may be interested in the work you're doing.
Hello Shiyao,
Yes, I'm really
