[PyQt] Next Releases of PyQt and SIP

Phil Thompson phil at riverbankcomputing.com
Tue Oct 20 09:41:44 BST 2009

On Fri, 16 Oct 2009 19:42:20 +0200, Giovanni Bajo <rasky at develer.com>
> On 10/16/2009 3:38 PM, Phil Thompson wrote:
>> On Fri, 16 Oct 2009 15:31:08 +0200, Giovanni Bajo <rasky at develer.com>
>> wrote:
>>> On 10/16/2009 10:10 AM, Phil Thompson wrote:
>>>> All outstanding bug reports against PyQt and SIP have been resolved -
>>>> if
>>>> you disagree then let me know.
>>>> I plan to release PyQt v4.6.1 and SIP v4.9.1 early next week.
>>>> BTW, the current PyQt snapshot will build against Qt v4.6-beta1.
>>> Hi Phil,
>>> I got some GC-related random crashes in a testsuite run after you fixed

>>> the QApplication destruction. I investigated them enough to see that 
>>> it's related to invokation of focusPolicy() or other focus-related 
>>> virtual methods on an already-deleted object, but they are hard to
>>> down and I am not sure whenever I will have a reproduction recipe
>>> Is there anything specific to focus stuff that rings a bell to you?
>> No. The obvious source of the problem is the QApplication being deleted
>> too
>> soon in relation to some other object.
> I delete all top-level widgets, flush all the events 
> (qApp.processEvents()), and run an explicit gc.collect() pass. I 
> actually don't know what else to do...
> I start to believe that it's a Qt problem rather than a PyQt's one; eg: 
> some globals somewhere in the focus code that is not reset by 
> QApplication's destructor and still points to some destroyed object.
> I'll have a further look.

Any progress? I'd prefer to revert to the existing broken behaviour (which
affects almost nobody) than introduce the potential for random
crash-on-exit "bugs".


More information about the PyQt mailing list