Currently, autogen.sh launches Python scripts using the "python"
executable. On many systems, "python" refers to Python 1.x, whereas
"python2" refers to Python 2.2. Thus, on these systems, we use Python
1.x in autogen.sh, even though Python 2.2 is available.
This patch updates autogen.sh and configure to look for Python in the
following locations (in order) for Python 2.0 or better: $PYTHON2,
$PYTHON, python, python2
If Python 2.0 or later is not installed, configure will report a
warning. The autogen.sh requires Python,
[[[
Require Python 2.0 or later for autogen.sh and configure. Look in the
following locations (in order) for Python 2.0 or better: $PYTHON2,
$PYTHON, python, python2
* autogen.sh:
Use ./build/find_python.sh to find Python 2.0.
* configure.in:
(PYTHON): Use $srcdir/build/find_python.sh to find Python 2.0.
* build/find_python.sh:
New file. Look in the following locations (in order) for Python 2.0
or better: $PYTHON2, $PYTHON, python, python2
]]]
Here's some examples to illustrate how the new code behaves:
Scenario 1:
* "python" refers to Python 1.x
* "python2" refers to Python 2.2
-> We use "python2", because "python" is too old.
Scenario 2:
* "python" refers to Python 2.2
* "python2" refers to Python 2.2
-> We use "python", because the user may have installed a local
version of python using the standard name "python", which they
want us to use instead of the system-wide "python2".
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 23 00:15:07 2005