Hello again,

> Still, I think this patch does too much code duplication. There should
> be only a single function that does the optional untracking; this then
> gets called from multiple places.

The point was to avoid slowing down the critical path of tuple creation
in the most common cases. If it is considered too hackish, then I agree
the other patch (tuple+dictopts-alt.patch) should be considered instead.

By the way, perhaps pybench should grow a GC test (e.g. derived from
Greg's script). What do you think?