Skip site navigation (1) Skip section navigation (2)

Re: Python 3.0 does not work with PL/Python

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: David Blewett <david(at)dawninglight(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, James Pye <lists(at)jwp(dot)name>, Marko Kreen <markokr(at)gmail(dot)com>
Subject: Re: Python 3.0 does not work with PL/Python
Date: 2009-05-29 15:38:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> David Blewett wrote:
>> I brought this up last August [1]. Zope has a working sandbox that 
>> they include in their distribution.

> How many python installations have this gadget? If the answer is "not 
> many" then it's not much good to us, unless someone wants to create 
> PL/zope-sandbox. Really, something like this should be part of a 
> standard python installation.

Yeah.  For one thing, how much trust can you put in a security mechanism
that hasn't been accepted upstream?  Given the history of this sort of
thing in Python, I'm not prepared to just assume that Zope got it right.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Zdenek KotalaDate: 2009-05-29 15:39:18
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Previous:From: Andrew DunstanDate: 2009-05-29 15:37:59
Subject: Re: plperl error format vs plpgsql error format vs pgTAP

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group