[Twisted-Python] reactor.run() do not return after reactor.stop()

Stanislav Yudin decvar at gmail.com
Sat Oct 10 12:50:01 EDT 2009

Thanks, but how can I pass control back to calling code after starting the
reactor? Or the idea is to run it in separate thread? I understand that main
idea on twisted is async processing, but this time I need to block the
calling code until response is received.

On Sat, Oct 10, 2009 at 6:10 PM, Johann Borck <johann.borck at densedata.com>wrote:

> Stanislav Yudin wrote:
> > Hi everyone,
> > I am having a problem with current twisted trunk (rev 27375). ...  So
> > the problem is that the first call to execute returns from
> > reactor.run() right after reactor.stop(), but second call to same
> > method of same instance do not return ever.
> > I believe I am doing something wrong, so please help with find out
> > what I've missed. Problem code attached.
> http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#WhycanttheTwistedsreactorberestarted
> But since you can do everything without restarting the reactor, that's
> no real limitation.
> hth, Johann
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://twistedmatrix.com/pipermail/twisted-python/attachments/20091010/9c895107/attachment.htm 

More information about the Twisted-Python mailing list