Horton

Re: Python 3.1 support

Joshua D. Drake <jd@commandprompt.com>

View thread View on postgr.es
From: "Joshua D. Drake" <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nathan Boley <npboley@gmail.com>, Peter Eisentraut <peter_e@gmx.net>, James Pye <lists@jwp.name>, pgsql-hackers@postgresql.org
Date: 2009-11-18T17:21:23Z
Lists: pgsql-hackers 
On Wed, 2009-11-18 at 12:06 -0500, Tom Lane wrote:
> Nathan Boley <npboley@gmail.com> writes:
> > Also, I am a little skeptical about this patch. I am sorry if this has
> > already been discussed, but would this mean that I need to choose
> > whether pl/python is built against Python 2.* or Python 3.*?
> 
> Yes.  That's exactly what I was complaining about upthread.  I'm not
> a Python user, but from what I can gather of the 2-to-3 changes,
> having to choose one at package build time is going to be a disaster.
> 

Agreed. We really need to have a plpython and plpython3. Heck this would
play nicely too because we support backward compatibility but also
upward version differences.

Joshua D. Drake


> 			regards, tom lane
> 


-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
If the world pushes look it in the eye and GRR. Then push back harder. - Salamander