[Twisted-Python] wxpython issues

Anthony Baxter anthony at interlink.com.au
Wed Apr 13 22:58:11 EDT 2005

The problem has been that wx's timer promises "no worse
than 1s" resolution. In practice, it's been utterly unable to 
hit less than 100ms on Windows, and 20ms on Linux is a
sometimes-thing. The only real solution that works robustly
is to run wx and twisted in separate threads. If there's a new
version of wx, you should probably try running wxreactor with
a LoopingCall set to 1ms, and see what timer it can hit 

Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.

More information about the Twisted-Python mailing list