On 6/25/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Gustavo Carneiro wrote:
> > However, PyObject_CallFunction does _not_
> > consume such an object reference, contrary to what I believed for
> > years.
>
> Why do you say that? It certainly does.
Yes it does. I could almost swear it didn
Gustavo Carneiro wrote:
> However, PyObject_CallFunction does _not_
> consume such an object reference, contrary to what I believed for
> years.
Why do you say that? It certainly does.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
ht
Sorry this is slightly offtopic, but I think it's important...
According to recent experiments tracking down a memory leak, it
seems that PyObject_CallFunction(func, "N", object) and
PyObject_CallFunction(func, "O", object) are doing exactly the same
thing. However, documentation says "The C
