elein wrote:
> Thanks, Scott.
>
> I believe that was Kevin Jacobs in a message to pgsql-general
> and I've sent him a message about being available for testing.
It sure is a shame the Python folks just decided to punt instead of
rolling up their sleeves and fixing the problem. Now a cascade of
d
Thanks, Scott.
I believe that was Kevin Jacobs in a message to pgsql-general
and I've sent him a message about being available for testing.
-elein
On Thursday 19 June 2003 14:27, scott.marlowe wrote:
> As I understand it, plpython currently relies on the rexec call /
> interface to function, a
I just didn't want anyone to say "no one complained".
That has been a reason some features were changed
without a lot of notice in the past. It is important to
understand who uses what.
And I have offered to do as much as I can at this
time. It is not as if I were whining about something
and b
elein <[EMAIL PROTECTED]> writes:
> I strongly protest the pulling of plpython.
I seem to have missed the part of this where you volunteer to fix it.
Complaining will not change anything; someone stepping up and doing the
work will change things.
regards, tom lane
--
As I understand it, plpython currently relies on the rexec call /
interface to function, and that functionality is going away, so SOMEONE
has to step up to the plate and change the way plpython is called in order
to keep it.
I do believe someone on hackers proferred an interest in doing this
I strongly protest the pulling of plpython.
Make it untrusted if necessary, but don't
pull it. The capabilities of plpython are
much too valuable to trash.
At this point I am available as a tester,
but not as a developer for any changes to the
interface. Drag me into the frey. I may also
be fr
