Zack Weinberg wrote:
> Automake's python.m4 should also define these if they are not already defined.
> Then, we split AM_PATH_PYTHON into the part that sets PYTHON, which is
> implemented
> in terms of the above macros (but still looks for both 2 and 3) and the part
> that
> does all the rest of
Here's what I think might be useful:
Add these three macros to Autoconf proper:
# AC_PYTHON_VERSION_RANGE_IFELSE([PROG], [MIN-VERSION], [MAX-VERSION =
next-major],
#[ACTION-IF-TRUE], [ACTION-IF-FALSE])
#
-
# Run
Or maybe AM_PYTHON3_PATH which requires Python3 so that the
interface of the original macro isn't changed.
My idea for having a separate options command was for the future: who
knows what incompatibilities python will create in the future. Other
options besides p3 vs p2 might be needed. In