[twisted-python] Communication between GUI thread and twisted thread.

Jean-Paul Calderone exarkun at divmod.com
Mon Jun 18 11:38:10 EDT 2007

On Mon, 18 Jun 2007 10:32:50 -0500, Chris Mellon <arkanes at gmail.com> wrote:
>On 6/18/07, 甜瓜 <littlesweetmelon at gmail.com> wrote:
>> > This is a terrible implementation for cooperation between wx and
>> > twisted. At the time it was written, it was acceptable, but you really
>> > should be using the wxreactor now.
>>Really? Oh! Maybe my knowledge is out of date. My opinion comes from
>>"The Twisted Documentation - Jan 9, 2007". It says:
>>"Twisted currently supports two methods of integrating wxPython.
>>Unfortunately, neither method will work on all wxPython platforms
>>(such as GTK2 or Windows). It seems that the only portable way to
>>integrate with wxPython is to run it in a separate thread."  ^_^
>>Therefore I followed that terrible implementation. Does wxreactor get
>>improvement? I will read 'choosing-reactor.html' throughly. Thank you.
>The docs are out of date in this case. Or rather, they are correct,
>but incomplete - Twisted now has support for a threaded reactor, and
>wxreactor has been updated to use this support, so the integration is
>now (mostly) seamless.

To nit pick, http://twistedmatrix.com/buildbot-supported/ shows what
Twisted has support for.  What Twisted has for wx is "code".  If you're
lucky, it might even behave in a useful manner for your particular
application. ;)

For anyone interested in something that might be called "support", please
get involved in Twisted development and contribute effort to finishing


More information about the Twisted-Python mailing list