[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>).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4