I almost rewritten pytracemalloc from scratch between versions 0.9 and 1.0. I wrote pytracemalloc 1.0 for Python 3.4. In this Python versions, "int" and "str" don't use freelists anymore. So tracking freelists become less important.

Python 3 uses free lists for the following object types:

• float
• tuple, list, set, dict
• bound method, C function, frame

Python 2 uses free lists for the following object types:

• int, float, unicode
• tuple, list, set, dict
• bound method, C function, frame

The tracemalloc module of Python 3.4 is written on top of the PEP 454 which is simpler than pytracemalloc 0.9.1 because it was not written for pytracemalloc, but to be able to use a custom memory allocator. Tracking freelists is not useful for such use case.
http://legacy.python.org/dev/peps/pep-0445/

pytracemalloc 0.9.1 had 3 options for free lists:

• Track free lists: track all Python objects. It is the recommended option.
• Don't track free lists: less accurate, but faster.
• Disable free lists: track all Python objects, slower.

On embedded devices, disabling free lists killed performances and could not be used. pytracemalloc 1.0 uses the option "Don't track free lists".