[Zope-Coders] Zope 2.7 configure finds wrong Python version

[Matt Behrens]

--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 10, 2003 at 10:39:13AM -0400, Guido van Rossum wrote:

> With the Zope head (i.e. Zope 2.7-to-be), on my Linux box, when I run
> the configure script, it finds IMO the wrong Python version.  Here's
> the relevant output:
>=20
>     Testing for an acceptable Python interpreter...
>=20
>       Python version 2.3b1+ found at /usr/local/bin/python
>       Python version 2.1.3 found at /usr/local/bin/python2.1
>       Python version 2.2.3+ found at /usr/local/bin/python2.2
>       Python version 2.3b1+ found at /usr/local/bin/python2.3
>       Python version 1.5.2 found at /usr/bin/python
>       Python version 2.2.2 found at /usr/bin/python2
>=20
>       The optimimum Python version (2.2.2) was found at /usr/bin/python2.
>=20
> The list of Pythons it found is correct, but why would it pick 2.2.2
> over 2.2.3+?  (Especially since we now officially require 2.2.3...)

Right at the top of the script, the target version can be set.

TARGET=3D"2.2.2"

Changing this should make it behave as you say it should.  2.2.2
would then be added to the beginning of ACCEPTABLE a few lines down.

Also, it says "optimimum" version, which should be fixed. :-)

(Re Barry's comment -- --with-python does seem to be supported.
But you also want to be able to provide some semblance of intelligence
for those who don't necessarily know where to look for their python
binary...)

--=20
Matt Behrens <matt@zigg.com> <URL:http://zigg.com/>

--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (OpenBSD)

iD8DBQE+5g32+xq4JbgNGlMRApIvAJ0RFNtmszGfhX3LqjniablI+/I2LACdHLSd
1JhBMKPffTbWqeNVpp/oSfE=
=zWJI
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--