[Twisted-Python] removing unsupported reactors in twisted 2.6: qt,

David Pratt fairwinds at eastlink.ca
Mon Sep 25 01:32:03 EDT 2006

Hi Glyph. I am not sure if I am the right person, but at the same time I 
don't wish to see the code removed. I see deprecation warnings and 
failed tests. Not great.

I am willing to help but I am not sure that I possess the expertise to 
solve all the issues. I am willing to commit to trying though, hopefully 
with the help of others. Perhaps I'll post on wxpython list to see if 
there are others willing to help.

wxpython and twisted are both important toolkits. Twisted integration is 
important to me for my own projects. I am hoping someone from the 
Chandler project thinks so too and feels that sharing in this effort is 
the right thing to do. I know there are a number of folks using 
wxreactor or threadedselectreactor in their wxpython code. It is 
reasonable that we shoulder some responsibility to help ourselves.


glyph at divmod.com wrote:
> On Mon, 25 Sep 2006 01:17:14 -0300, David Pratt <fairwinds at eastlink.ca> 
> wrote:
>> Hi all. I am also using the threadedselectreactor in wx without 
>> problems. I have only just read these posts and cannot understand any 
>> reasoning to drop it. What am I missing?
> "If it's not tested, it's broken."
> The point is not that I want to drop this code from Twisted.  In fact, 
> far from it, I would like Twisted to support as many toolkits as possible.
> The point is that these reactors are currently excluded from automated 
> test coverage, and have no maintainers.  That means that they do not 
> currently work as well as the other reactors, but more seriously, if 
> they were to be *completely* broken (say, start raising exceptions upon 
> import), nobody on the Twisted team would know until users started 
> complaining, and most likely users would not complain until well after 
> we had already produced a broken release.
> We could add automated test coverage relatively easily, *IF* someone 
> would volunteer to at least look at the results of that coverage and 
> contribute some fixes.  Perhaps you were not even aware that there are 
> reliability problems with threadedselectreactor.  To see an example of 
> the problem, run "trial --reactor threadedselect twisted".
> Would you volunteer to have a look at some of these problems and try to 
> fix them?  I have no idea how many people are using Twisted in 
> conjunction with wxwindows today, but you would be a hero to all of 
> them, I'm sure :).

More information about the Twisted-Python mailing list