Guido van Rossum wrote: > But this still takes time, and most tuples never make it into GC, so > it's wasted time, isn't it? I agree. The idea I though of last night was to have the GC special case certain objects. It could know about tuples. After collecting the first generation any surviving tuples that don't refer to objects with the GC flag could be untracked. We might even generalize it by untracking objects that don't have a tp_clear method and don't refer to GC objects. BTW, I also looked into the train algorithm last night. It's cool because it never examines the entire set of objects (unless they all happen to be a big cyclic garbage struture). Unfortunately I don't think it can be adapted for Python. > I'd put such code in tuplevisit (assuming it's safe to call GC_UnTrack > there). That would be slick. I don't know if it's safe without looking at the code but it could probably be made so. Neil
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