[Python-Dev] Bizarre new test failure

[Tim Peters]

[Neil Schemenauer]
> I wonder if some new cyclic garbage structure needs two gc.collect()
> passes in order to break it up.

Can you dream up a way that can happen legitimately?  I haven't been able
to, short of assuming the existence of a container object that isn't tracked
by gc.  Else it seems that all the unreachable cycles that exist at any
given time will be found by a single all-generations gc pass (either that,
or gc is busted <wink>).