Ivan Shmakov wrote:

>  > You can currently run with --with-python=/usr/bin/python2.5 to
>  > force using version 2.5.
> 
>       BTW, there're some Python-related Autoconf code in Automake and
>       in the Autoconf Macro Archive, e. g.:
> 
> $ dpkg -S python.m4 
> autoconf-archive: /usr/share/autoconf-archive/ax_boost_python.m4
> autoconf-archive: /usr/share/autoconf-archive/ax_python.m4
> autoconf-archive: /usr/share/autoconf-archive/ax_with_python.m4
> autoconf-archive: /usr/share/autoconf-archive/az_python.m4
> automake: /usr/share/aclocal-1.10/python.m4
> $ 
> 
>       At the first glance, `az_python.m4' seems to be the most
>       suitable.  Apparently, it doesn't depend on `python-config', but
>       accesses the same configuration storage using the ways native to
>       Python.
> 
>       Is this check suitable for GRASS?

Why use anything other than python-config? If some other mechanism
produces the same result, there's no benefit; if it produces a
different result, it's presumably wrong.

If there's a standardised way to do something, using any other
mechanism is usually a maintenance headache waiting to happen.

-- 
Glynn Clements <[EMAIL PROTECTED]>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to