[Zope-Coders] Zope 2.7 configure finds wrong Python version
Guido van Rossum
guido@python.org
Tue, 10 Jun 2003 13:11:15 -0400
> > 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:
> >
> > Testing for an acceptable Python interpreter...
> >
> > 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
> >
> > The optimimum Python version (2.2.2) was found at /usr/bin/python2.
> >
> > 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="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. :-)
Hm. There's also a list of "ACCEPTABLE" versions. Unfortunately it
appears out of date (2.3b1 is not on it). Plus, I don't know if a
trailing sub-version or "+" is accepted or not. Etc.
--Guido van Rossum (home page: http://www.python.org/~guido/)