On Thu, 25 Aug 2011 18:08:17 +0100, Phil Thompson
wrote:
> On Sat, 13 Aug 2011 10:05:14 -0600, Kovid Goyal
> wrote:
>> This bug has been present for a very long time. As a workaround in my
>> projects,
>> I disable the automatic garbage collector and run garbage collection
>> manually
>> in the
On Sat, 13 Aug 2011 10:05:14 -0600, Kovid Goyal
wrote:
> This bug has been present for a very long time. As a workaround in my
> projects,
> I disable the automatic garbage collector and run garbage collection
> manually
> in the GUI thread via QTimer. Here's the code to do that:
>
> class Garba
On 2011-08-13 18:05, Kovid Goyal wrote:
> This bug has been present for a very long time. As a workaround in my
> projects,
> I disable the automatic garbage collector and run garbage collection manually
> in the GUI thread via QTimer. Here's the code to do that:
>
> class GarbageCollector(QObje
This bug has been present for a very long time. As a workaround in my projects,
I disable the automatic garbage collector and run garbage collection manually
in the GUI thread via QTimer. Here's the code to do that:
class GarbageCollector(QObject):
'''
Disable automatic garbage collectio
Hello Phil,
I believe to have found a subtle bug in PyQt in
combination with the Python garbage collector.
Here is what I think that happens :
- A QObject is constructed in one thread,
and this QObject construction contains a cyclic
dependency.
- this construction will not be deleted with
