Good news. On the most recent snapshot 20070723 this problem is solved.
Our plan will be to move to the latest and never really land on 4.2.
David Boddie wrote:
We have just migrated code from using PyQt-4.2 on Qt-4.2 to using
PyQt-4.2 on Qt-4.2. This has revealed what looks like a very serious bug
in the signal handling code for PyQt-4.2.
OK. Some things to check first:
_______________________________________________
PyQt mailing list [email protected]
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
