memory leaks in 1.5.2 Python interpreter

[Michael McCarthy]

We have observed memory leaks in the 1.5.2 Python interpreter under
Purify.

If we check for new leaks immediately before and immediately after
invoking PyEval_CallObject, we often see a leak originating in
PyTuple_New as invoked by eval_code2.

Can anyone tell me whether or not later versions of Python have
addressed any memory management problems? We would like to know if
moving to a newer version will clear up any memory leaks.

Thanks for your help.

Michael McCarthy

//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
Michael McCarthy                     TCSI Corporation
michael at tcsi.com                     1080 Marina Village Parkway
(510) 749-8739                       Alameda, CA 94501-1046