I see neilc has hacked on it very recently to reduce memory leaks. I
take that as both good and bad signs.
We're a [ small ] python shop, and would be most interested in being
able to simplify our life through doing some things in plpython
instead of pl/pgsql where appropriate. Keeping our constants and so
forth in the appropriate python module would make things ever so much
simpler here and there at the very least.
But we've never hacked on the backend, nor at the C python API level.
But I see no reason why not to start now -- lurked here for many a
year. For example, I see that plpython functions cannot be declared
to return void. That can't be too tough to remedy. Implementing the
DBI 2.0 API interface to SPI can wait another day.
On Feb 24, 2006, at 11:08 PM, Joshua D. Drake wrote:
> James Robinson wrote:
>> I'm interested in poking though and taking a shot at getting my
>> feet wet with pl/python. I see the file is copyright Andrew Bosma
>> -- is he still around perhance? Is anyone currently the 'owner' ?
> To my knowledge there is no current maintainer of plPython and it
> definitely needs some love.
>
>>
>> ----
>> James Robinson
>> Socialserve.com
>>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 1: if posting/reading through Usenet, please send an appropriate
>> subscribe-nomail command to majordomo@postgresql.org so that
>> your
>> message can get through to the mailing list cleanly
>>
>
>
> --
> The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> Managed Services, Shared and Dedicated Hosting
> Co-Authors: PLphp, PLperl - http://www.commandprompt.com/
>
----
James Robinson
Socialserve.com