Python 2.7.3, C++ embed memory leak?

[Qi]

On 2012-5-29 23:29, Ulrich Eckhardt wrote:
>
> Call the pair of functions twice, if the reported memory leak doesn't
> increase, there is no problem. I personally wouldn't even call this a
> leak then, but that depends a bit on the precise definition.

I should still call it a memory leak though it seems less harmful.
And it causes trouble that I have difficulty to distinguish if
the leaks are from Python or from my binding code, if I add binding
between that pair of functions.


-- 
WQ