On Wed, 18 Jun 2008 18:03:49 + (UTC), Kevin Watters
<[EMAIL PROTECTED]> wrote:
> There's a comment in siplib.c:5300ish in the sip_api_is_py_method
> function that I'll reproduce here:
>
> /*
> * Note that the callable is never garbage collected. The main
> * reason for this is that it's not
Kevin Watters wrote:
> I'm tracking down a memory leak in my app--and I think it's boiling
> down to a virtual method on one of my classes that has an extra
> reference, one not coming from any Python object.
Hi Kevin, hi Phil, hi all,
Okay, Kevin, you MUST be reading my mind because, first thin
There's a comment in siplib.c:5300ish in the sip_api_is_py_method
function that I'll reproduce here:
/*
* Note that the callable is never garbage collected. The main
* reason for this is that it's not possible to get hold of the
* method cache without make incompatible changes to the SIP
* AP
