```python
# Literal 9 is an object
b = 9

# Reference count of object 9 
# becomes 0.
b = 4
```
In the above example, the value 9 is an object and thus memory is allocated for it to be assigned to variable b. At this point, it has a reference count value of 1. Once the variable b is reassigned to 4, the reference count of value 9 decrements to 0. Hence, 9 is deallocated from memory.

Reference Counting Example

Each object in Python also comes with its own data value called a reference count. An object's reference count is increased each time it is referenced by other objects and decreased when a reference is removed. When an object's reference count reaches zero, it is deallocated from memory. Reference counting by itself is a somewhat limited and primitive way to manage memory, and doesn't catch all objects in need of deallocation. This is why it is paired with another garbage collection strategy.

Saint Olaf College

Some programming languages require that the programmer manually deallocate memory. However, Python does this automatically through the use of a garbage collector. In short, a garbage collector will deallocate memory for any objects that are deemed to be no longer necessary for the program. Python implements two strategies for garbage collection:
- Reference Counting
- Generational Garbage Collection

Garbage Collection

Geeks for Geeks is a website that offers information on a variety of programming languages, tips for coding interviews, and ideas for programming projects:  https://www.geeksforgeeks.org/python-programming-language/

Geeks for Geeks Python Programming Language

https://stackify.com/python-garbage-collection

Stackify: Python Garbage Collection

Reference Counting

Sometimes objects have reference counts above 0, but no longer have references to it. These objects should be deallocated, but reference counting alone won't deallocate them. These are called unreachable objects. Garbage collectors will look for these unreachable objects and deallocate them.
Generational garbage collection runs under the assumption that most objects have a very short lifespan and can be deallocated shortly after creation. The older an object is, the less likely it is to become unreachable. This assumption is true for many Python programs. So, all objects are organized into three categories, referred to as generations. Garbage collection occurs separately for each generation and at different frequencies. All new objects start at generation 0 and if they survive a garbage collection that surveys generation 0, they are elevated to generation 1, which is surveyed less often. If they survive a garbage collection across generation 1, they move on to generation 2, which is the least surveyed.

Learn Before

Related

Learn After