Tracking Down a Python Memory Leak (Part 2) | Dark Hacker News