From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | James William Pye <lists(at)jwp(dot)name> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Python 2.7 deprecated the PyCObject API? |
Date: | 2010-08-14 16:08:41 |
Message-ID: | 29560.1281802121@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
James William Pye <lists(at)jwp(dot)name> writes:
> On Aug 13, 2010, at 5:20 PM, Tom Lane wrote:
>> I see several calls in plpython.c that seem to refer to PyCObject stuff.
>> Anybody have any idea if we need to do something about this?
> Well, we should at least be checking for an exception here anyways:
> proc->me = PyCObject_FromVoidPtr(proc, NULL);
> PyDict_SetItemString(PLy_procedure_cache, key, proc->me);
> if (proc->me == NULL) complain();
Just to clarify, you're recommending something like
proc->me = PyCObject_FromVoidPtr(proc, NULL);
+ if (proc->me == NULL)
+ elog(ERROR, "could not create PyCObject for function");
PyDict_SetItemString(PLy_procedure_cache, key, proc->me);
correct? (Hm, and it looks like we'd better move the pfree just above that...)
> AFA a better fix is concerned, the shortest route would seem to be to
> use the new capsule stuff iff Python >= 2.7.
Yeah, and since we'll have to back-patch it, a fairly noninvasive patch
would be nice. Will you work on that?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | James William Pye | 2010-08-14 18:14:26 | Re: Python 2.7 deprecated the PyCObject API? |
Previous Message | Tom Lane | 2010-08-14 15:49:46 | Re: BUG #5608: array_agg() consumes too much memory |