| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Nathan Boley <npboley(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, James Pye <lists(at)jwp(dot)name>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Python 3.1 support |
| Date: | 2009-11-18 17:21:23 |
| Message-ID: | 1258564883.20737.2.camel@jd-desktop.unknown.charter.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-11-18 at 12:06 -0500, Tom Lane wrote:
> Nathan Boley <npboley(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-18 17:23:28 | Re: Patch - Reference Function Parameters by Name |
| Previous Message | Kevin Grittner | 2009-11-18 17:09:52 | Re: RFC for adding typmods to functions |