On 02:24 am, drsali...@gmail.com wrote: >On Tue, Jul 17, 2012 at 12:53 PM, <exar...@twistedmatrix.com> wrote: >>On 03:40 pm, drsali...@gmail.com wrote: >> >> >> >>Strangely, this doesn't give the report until after the sleep >> >>finishes... ? >> >>What's strange about that? "time.sleep(10)" doesn't mean "immediately >>print out debug information". >Well, if you read the whole thread, I believe you'll see that this was >intended to print some debugging information without needing to wait >for >the process to terminate.
I don't think anything in the thread suggested that this approach will circumvent a time.sleep(10) call. In any case, it won't. Why is there a time.sleep(10) call there at all? Does it do anything except cause a problem? Jean-Paul > >> >> >However, it always appears to print the debug tracebacks for the >> >deferred >> >named - in this case, d. It doesn't appear to be selecting the >>correct >> >deferred(s) to print. >> >> >>All it does is print the debug information for the Deferred you got >>the >>_debugInfo attribute from. > >Um, yes, I was kind of saying that. Sadly though, this renders it >ineffective for the purpose it was suggested for. _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
