Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment

From: Lou Picciano <loupicciano(at)comcast(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-testers(at)postgresql(dot)org, James William Pye <lists(at)jwp(dot)name>
Subject: Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment
Date: 2010-09-13 01:20:55
Message-ID: 1964688383.249167.1284340855417.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-testers

I would be willing to accept the 'pilot error' tag (I have no instrument rating in this type), but...

Isn't it common to have multiple versions of libs in an environment? We have several versions of many things, used in different settings - often specifically for purposes of version testing. For example, we kept the python2.4 implementation because we have some code which (we believe) may depend on it. By the way, we have no immediate interest in pl/Python; this compilation attempt was only for testing purposes...

Yes, the 2.4 version of python is found first in our PATH environment. What seems strange in this case, though, is that - apparently? - no combination of configure options or env variables lets us designate one version consistently. The configure script is itself mixing versions:

--with-python \

--with-includes=/usr/local/include/python3.1:/usr/local/include:/usr/local/ssl/include \

--with-libraries=/usr/local/lib/python3.1:/usr/local/lib:/usr/local/ssl/lib \

Setting env PYTHON or PYTHONPATH didn't seem to have any impact.

We are also not such python mavens as to be anything near expert with it...

- Lou Picciano

----- Original Message -----
From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: "James William Pye" <lists(at)jwp(dot)name>
Cc: pgsql-testers(at)postgresql(dot)org
Sent: Sunday, September 12, 2010 6:23:23 PM
Subject: Re: [TESTERS] Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment

James,

> On Sep 11, 2010, at 4:11 PM, Josh Berkus wrote:
>> So, is this a bug? Should we be fixing it before release?
>
>
> Yes to both.

Hmmm. Tom Lane says "pilot error" because there are two versions of
Python in the path. Specifically:

"In particular, how'd those 3.1 references get in there when the python
version in $PATH is 2.4? It's for damn sure we didn't introduce those."

If Tom is incorrect, please take up the thread on -BUGS. I don't know
enough about python libs in builds to argue either way.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
-
HOWTO Alpha/Beta Test:
http://wiki.postgresql.org/wiki/HowToBetaTest
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-testers

Browse pgsql-testers by date

  From Date Subject
Next Message Lou Picciano 2010-09-13 02:10:46 pg_upgrade 9b4 -> 9rc1 odd behavior with -u (non-)postgres
Previous Message Josh Berkus 2010-09-12 22:23:23 Re: Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment