Python Memory Manager

[Paul Rubin]

"Martin v. Löwis" <martin at v.loewis.de> writes:
> That's not exactly true, i.e. it isn't mark-and-sweep, but some similar
> scheme that allows incremental collection without write barriers. This
> particular scheme heavily relies on refcounting itself (specifically,
> an object is garbage in a certain generation when all references to
> it come from the same generation).

Ah, thanks.  I made another post which I guess is also somewhat wrong.