http://evanjones.ca/python-memory.html

http://utcc.utoronto.ca/~cks/space/blog/python/DebuggingPythonMemoryLeaks

I think these are where I got my ideas about memory leaks in Python.  I'm not trying to challenge anything, just pass along what I've read.  The early version of Geom seemed to have a leak, and the smoothing functions for TDMT still seem to have one.  At least one PoserPython script exists out there (it might be a later version of Walk This Way?) which goes to great lengths using the gc module to try to plug an apparent memory leak, according to the comments in the script.

But I'm just looking this up tonight because I wasn't able to get any time in today on Python, so I'm trying to contribute some little bit to the matter, anyway.

And, really, it's not a huge big problem, in the current situation.  The earliest versions of the script in this thread (well before it was TDMT) had RAM consumption problems, readily grabbing up hundreds of megs in a run.  A few MBs here and there is no problem, compared to that.  I'm just all flinchy about such things, after that early experience....

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.