[PyKDE] PyQt 3.12 introduces deadlock with QCustomEvent's destructor.

[Ken Godee]

Toby Dickenson wrote:

> On Monday 16 August 2004 17:09, Truls A. Tangstad wrote:
> 
>>It's a hard pill to swallow though, since this means our application
>>will have to be infected with Qt in layers not at all related to GUI,
>>just because GUI components can register callbacks etc. in them.
> 
> 
> Indeed. We have been making the same mistake, although without the obvious ill 
> effects of your example.
> 
> Where does this limitation come from? The Qt threading documentation doesnt 
> mention a requirement to use QThread, so I assume it comes from PyQt 
> somewhere.....
> 
> Is there any other way to signal an event of any kind into Qt's event loop 
> from a non-QThread thread?
> 

We found Boudewijn Rempt's article to be helpfull.

"Writing Multithreaded GUI Applications with Python"

http://www.informit.com/articles/article.asp?p=30708&seqNum=1