[C++-sig] memory leaks using the "manage_new_object" return policy...

[Stefan Seefeld]

Kevin Jones wrote:
> Hi,
> 
> I am using the manage_new_object return policy to wrap
> "newed" C++ object in an effort to conserve memory.
> 
> Even though I am deleting the returned object in
> Python and invoking the Python garbage collector I
> still have a leak.

The obvious question: Are you sure your C++ objects are
not deleted, while the python (wrapper) objects are ?

Regards,
		Stefan