Re: automake and pyconfigure: a future integration? (was: Re: [PATCH] AM_PATH_PYTHON: try "python2" et al. first)

Quite a lengthy response for such a simple inquiry! Really, I'd just like to get gobject-introspection to compile on Arch Linux. The problem is that gobject-introspection's configure.ac has the line AM_PATH_PYTHON([2.5]) but gobject-introspection can't actually work with Python 3 or higher (the

Re: automake and pyconfigure: a future integration? (was: Re: [PATCH] AM_PATH_PYTHON: try "python2" et al. first)

>> > Me too, mostly. But I agree that there is an underlying issue (albeit > not major). > >> The "Future Changes to this Recommendation" >> section of PEP 394 anticipates changing the `python' symlink to >> `python3' at some point in the future. This has already happened in Parabola, Arch and ot

automake and pyconfigure: a future integration? (was: Re: [PATCH] AM_PATH_PYTHON: try "python2" et al. first)

Severity: wishlist [+cc bug-automake, +cc bug-pyconfigure] Reference: On 12/13/2012 11:15 AM, Jack Kelly wrote: > Kerrick Staley writes: >> Usually, when AM_PATH_PYTHON is invoked with an argument of the form >> 2.X, it

Re: [PATCH] AM_PATH_PYTHON: try "python2" et al. first

Kerrick Staley writes: > Usually, when AM_PATH_PYTHON is invoked with an argument of the form > 2.X, it means that only a Python 2 interpreter should be used, and not > a Python 3 interpreter. However, the "python" command invokes a Python > 3 interpreter on some systems (see [1]), so if we try "p

[PATCH] AM_PATH_PYTHON: try "python2" et al. first

When checking for a suitable Python version, try "python2", "python 2.7", "python2.6", etc. before trying "python". Usually, when AM_PATH_PYTHON is invoked with an argument of the form 2.X, it means that only a Python 2 interpreter should be used, and not a Python 3 interpreter. However, the "pyth