As far as I know, we don't actually use anything wx-specific for Twisted
integration; we simply run Twisted in a non-UI thread, with the
standard/default reactor implementation. So, I don't think we have any
institutional knowledge to offer in support of the wxreactor or
threadedselectreactor.
At 09:31 AM 9/25/2006 -0700, Robin Dunn wrote:
FYI
-------- Original Message --------
Subject: [wxPython-users] wxreactor and threadedselectreactor need our help
Date: Mon, 25 Sep 2006 10:22:41 -0300
From: David Pratt <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
Hi all. Recently, a thread was started by the developers of Twisted to
remove the wxreactor and threadedselectreactor from the Twisted code
base as of the 2.6 release. These reactors are an essential element of
the Twisted networking framework used by wxpython developers for our gui
platform.
The bottom line is that if as a community of wxpython developers, we are
not stepping up to support these tools, support for our platform will
disappear. This is disconcerting and I have volunteered to assist but
others are needed to help supply fixes to automated unit tests that are
failing, deprecation warnings and to commit patches. Assistance is also
needed to maintain a buildbot that will help keep these reactors
available to the community (and tested on mulitiple platforms).
I am hoping that the Chandler project can identify a person also since
twisted integration is fundamental to their wxpython app.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
