Hm, look like this issue is and old and known problem, at least to some. I found it mentioned in <URL: http://stackoverflow.com/questions/17624114/how-to-diagnose-potential-memory-leak-in-python-program > from 2013-07-12.
To me, the issue seem similar to <URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=151489 > which was supposed to have been fixed in 2002, but perhaps the CVS commit was reverted? Version 0.5.4.4 should have the fix, according to BTS. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
