Re: [Twisted-Python] twisted eats the error

2017-02-13 Thread steven meiers
> > [SNIP] > > The “Unhanded error in Deferred” isn’t coming from your call to > deferToThread, it is coming from your task.LoopingCall.  When you > invoke .start() on your LoopingCall instance, it returns a Deferred, > which fires its assigned callback handler when you call .stop() on > the Loo

Re: [Twisted-Python] twisted eats the error

2017-02-13 Thread L. Daniel Burr
Hi Steven, On February 13, 2017 at 12:01:49 PM, steven meiers (commercial...@yahoo.de) wrote: > Sorry, your code example and your explanation don’t make clear what > you expect to happen, and when.  When you say “the first method that > is called from my code”, are you referring to  aSillyBlock

Re: [Twisted-Python] twisted eats the error

2017-02-13 Thread steven meiers
> Sorry, your code example and your explanation don’t make clear what > you expect to happen, and when.  When you say “the first method that > is called from my code”, are you referring to  aSillyBlockingMethod, > or runEverySecond?  In the deferToThread case, you are calling the > former; in the

Re: [Twisted-Python] twisted eats the error

2017-02-13 Thread L. Daniel Burr
Hi Steven, On February 13, 2017 at 9:24:03 AM, steven meiers (commercial...@yahoo.de) wrote: hi, there is a abvious error in the code at the end. since i know next to nothing about threads i thought maybe a print statement in the code that is actually doing the work would give me some pointers

[Twisted-Python] twisted eats the error

2017-02-13 Thread steven meiers
hi, there is a abvious error in the code at the end. since i know next to nothing about threads i thought maybe a print statement in the code that is actually doing the work would give me some pointers. if im not mistaken, it is: def callWithContext in python/context.py as it turns out it does