Re: [Fwd: memory leaks in python interface [was Hash view questions]]

Well, I should get off my butt here.   I agree that the metakit
interface needs to be rewritten and I have started a swig'd version
that is going slowly.  The first pass is a "low-level" interface that
acts like C++.  If anyone wants to help me flesh it out, I'll start a
sourceforge repository so we can make the second pass to be more
pythonic.

Brian Kelley

On 3/13/06, [email protected] <[email protected]> wrote:
>
>  Ralf Schmitt schrieb:
> >
> > depending on the compiler and optimizations being used.
> > In case it uses the "memcpy copy constructor", the _key member is being
> > decrefed one too many times.
> >
> >
> > I'll send another patch.
>
> Eagerly awaited!  In the meantime I think I'll use your earlier patch, as it
> doesn't cause segfaults here.
> _____________________________________________
> Metakit mailing list  -  [email protected]
> http://www.equi4.com/mailman/listinfo/metakit
>
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit