| From: | James William Pye <lists(at)jwp(dot)name> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-testers(at)postgresql(dot)org, Lou Picciano <loupicciano(at)comcast(dot)net> |
| Subject: | Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment |
| Date: | 2010-09-13 03:26:41 |
| Message-ID: | E3FCF74E-92F7-481C-A61C-8C477E4A07BB@jwp.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-testers |
On Sep 12, 2010, at 8:19 PM, Tom Lane wrote:
> James William Pye <lists(at)jwp(dot)name> writes:
>> I think it kept favoring python2 when I wanted python3 as both were in $PATH.
>
> AFAICS, it'll pick whichever version is executed when you say "python".
> Doesn't seem like an unreasonable behavior to me.
Perhaps reasonable, but:
jwp(at)torch[]:python/release31-maint/Include 0% ls /src/build/py32pg90/bin/py*
/src/build/py32pg90/bin/pydoc3 /src/build/py32pg90/bin/python3-config /src/build/py32pg90/bin/python3.2-config
/src/build/py32pg90/bin/python3 /src/build/py32pg90/bin/python3.2
3.x doesn't have a "python" link by default, so the user will have to make one in order to get ./configure to select it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-09-13 22:17:22 | Re: pg_upgrade 9b4 -> 9rc1 odd behavior with -u (non-)postgres |
| Previous Message | Tom Lane | 2010-09-13 03:19:48 | Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment |