[Python-Dev] Lazily GC tracking tuples

Neil Schemenauer nas@python.ca
Tue, 7 May 2002 17:46:54 -0700

I'm not sure I like this approach.  Slowing down PyTuple_SET_ITEM to
optimize a micro-benchmark seems dubious.  However, dropping the number
of tracked objects by 50% _does_ seem worthwhile.  Couldn't we get the
same effect by checking and untracking the appropriate tuples after
finishing a gen1 collection?  Each tuple would be checked once and short
lived tuples will probably not be checked at all.