Re: question about the GC implementation

2009-10-05 Thread Francis Moreau
On Oct 3, 11:58 pm, ryles wrote: > >     Only objects with GC_TENTATIVELY_UNREACHABLE still set are > candidates for collection.  If it's decided not to collect such an object > (e.g., it has a __del__ method), its gc_refs is restored to GC_REACHABLE > again. Ok so it happens _only_ w

Re: question about the GC implementation

2009-10-03 Thread ryles
On Oct 2, 11:20 am, Francis Moreau wrote: > Hello, > > I'm looking at gcmodule.c and in move_unreachable() function, the code > assumes that if an object has its gc.gc_refs stuff to 0 then it *may* > be unreachable. > > How can an object tagged as unreachable could suddenly become > reachable late

question about the GC implementation

2009-10-02 Thread Francis Moreau
Hello, I'm looking at gcmodule.c and in move_unreachable() function, the code assumes that if an object has its gc.gc_refs stuff to 0 then it *may* be unreachable. How can an object tagged as unreachable could suddenly become reachable later ? Thanks -- http://mail.python.org/mailman/listinfo/p