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
David Boddie wrote:
OK. Some things to check first:
1. Which platform are you running on?
2. Are the signal-slot connections direct or queued?
3. Do the Python objects live in a different thread to the listening
objects?
This is running on linux, Centos4. We are using direct connections
On Tue, 24 Jul 2007 14:54:50 -0700, Peter Shinners 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.
>
> We have Python "value" objects derived from QObje
On mar, 2007-07-24 at 14:54 -0700, Peter Shinners 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.
You may want to run latest SIP/PyQt snapshots, as t
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.
We have Python "value" objects derived from QObject. These emit a value
change event to other values and to liste
