Garbage Collector in Python - explain

Python's garbage collector (GC) primarily uses reference counting to manage memory, immediately deallocating objects when their reference count drops to zero. To handle circular references, which reference counting cannot resolve, it employs a generational garbage collector.

Mechanics and Why Both Are Needed

Example and Practical Considerations

Consider two objects, a and b, referencing each other:

class Node:
    def __init__(self):
        self.ref = None
a = Node()
b = Node()
a.ref = b
b.ref = a
# Even if 'a' and 'b' are no longer referenced externally,
# their internal ref counts remain 1, preventing ref counting from cleaning them.

In CPython, reference counting is the primary mechanism, offering immediate deallocation. The generational collector acts as a fallback for the less common, but critical, scenario of circular references.

In the interview, also mention that while Python's GC is mostly automatic, the built-in gc module allows manual control (gc.collect()) and inspection (gc.get_count(), gc.get_threshold()). In production, focus on designing code to avoid circular references for large objects rather than frequent manual GC tuning, as it can introduce unpredictable performance overhead.