[Twisted-Python] Odd behavior in IRC logbot

Bob Ippolito bob at redivi.com
Sat Oct 25 15:37:47 EDT 2003

On Oct 25, 2003, at 1:44 PM, Phillip J. Eby wrote:

> At 03:21 AM 10/26/03 +1100, Andrew Bennetts wrote:
>> On Sat, Oct 25, 2003 at 10:07:42AM -0400, Phillip J. Eby wrote:
>>     def clientConnectionFailed(self, connector, reason):
>>         print "connection failed:", reason
>>         reactor.stop()
>>     ...
>> Perhaps clientConnectionFailed is being triggered, instead of
>> clientConnectionLost (which has no delay at all, as you can see)?  
>> (The docs
>> don't clearly say this, but ccF is called when there was no connection
>> established, and ccL is called when a connection was made and then
>> disconnected).
> But shouldn't reactor.stop() cause the process to exit, rather than 
> hang?  I'm running the logbot under daemontools, so if it exited, it 
> should be restarted.  But that's not what I'm seeing.  Instead, the 
> process just goes idle.

I've seen reactor.stop() hang if there's threads happening.


More information about the Twisted-Python mailing list