>> * Have the reactor run in a seperate thread from wx (making sure to
>> use reactor.run(installSignalHandlers=False))
>> * Spawn threads from wx->Twisted in the proper way: use
>> reactor.callFromThread(reactor.callInThread(someCall))
A small point, but my code snippet example should have been:
Reza Lotun wrote:
* Have the reactor run in a seperate thread from wx (making sure to
use reactor.run(installSignalHandlers=False))
* Spawn threads from wx->Twisted in the proper way: use
reactor.callFromThread(reactor.callInThread(someCall))
I'd second that -- I've used the pattern described h
Reza Lotun wrote:
Hi Gabriel,
I don't quite understand your question. Do you mean to say that you
have written some code with wx and Twisted in an integrated event
loop, and are doing something like reactor.callInThread(someCall), and
when you call reactor.stop the app doesn't exit? AFAIK, any
Hi Gabriel,
I don't quite understand your question. Do you mean to say that you
have written some code with wx and Twisted in an integrated event
loop, and are doing something like reactor.callInThread(someCall), and
when you call reactor.stop the app doesn't exit? AFAIK, any thread
spawning goes
Hello everyone,
I have written some code using Twisted that spawns threads and another
using wxPython integration. For some reason when reactor.stop() is
called they don't always exit. I suspect that the reactor is waiting on
the threads to finish, which they apparently don't do, and as for th
