On 12/30/2010 11:39 AM, Even Rouault wrote:
I guess my question actually boils down to: how can I specify in the
configure phase, which python to use for the bindings? E.g. I have both
2 and 3 on my system, and 3 is the default, but I want gdal to build and
install the bindings for 2. Could I s
> I guess my question actually boils down to: how can I specify in the
> configure phase, which python to use for the bindings? E.g. I have both
> 2 and 3 on my system, and 3 is the default, but I want gdal to build and
> install the bindings for 2. Could I specify
> --with-python=/usr/bin/python2
On 12/29/2010 06:06 PM, Even Rouault wrote:
Vincent,
you didn't mention which GDAL version you use. Since GDAL 1.7.0, the Python
bindings work with both python 2.X and 3.X. But I see that the autoconf check
for python isn't python3 ready indeed. So you can ignore the configure errors
and just cd
Vincent,
you didn't mention which GDAL version you use. Since GDAL 1.7.0, the Python
bindings work with both python 2.X and 3.X. But I see that the autoconf check
for python isn't python3 ready indeed. So you can ignore the configure errors
and just cd swig/python and build the buindings from
Oops, wrong conclusion. Seems more complicated than I thought, as there
are some python checks in configure that use python...
Lets change this into a question:
as I have both python2 and python3, with /usr/bin/python linking to
python3 (so python3 is the default), and gdal's python extension
Hi,
some time ago, Arch linux made the rather bold decision to have python3
as system python default, of course with a /usr/bin/python2 alternative
sitting next to it. However, as the /usr/bin/python link is pointing to
/usr/bin/python3, gdal's swig python module's setup.py is being called
wi
