[Gdal-dev] Python next-gen bindings enabled in trunk

[Mateusz Loskot]

Frank Warmerdam wrote:
> Mateusz Loskot wrote:
>> Frank Warmerdam wrote:
>>> Vincent Schut wrote:
>>>> My preferences:
>>>>
>>>> make: runs setup.py build make install: - runs setup.py install for
>>>> bindings - separately installs scripts in prefix, alongside the
>>>> other gdal utilities.
>>> Folks,
>>>
>>> This also sounds good to me, though I'd be ok with installing by
>>> default in the Python tree as long as there is an easy way (driven by
>>>  configure) to place stuff elsewhere.  Something like we do now with
>>> --with-pymod-dir.
>>
>> Folks,
>>
>> I concur Frank's suggestion.
>> Personally, I prefer to not to mess standard prefix locations
>> with any files during process of development (building, testing,
>> fixing). Ideally, I'd like to be able to use python bindings *without*
>> necessity of running any install steps, as it is possible with old-gen
>> python, though AFAIK it's not easy or even feasible with the new
>> bindings.
> 
> Mateusz,
> 
> I do this all the time with the new bindings!  It's just that the
> PYTHONPATH item I insert is messy.
> 
> warmerda at amd64[1]% echo $PYTHONPATH
> /home/warmerda/gdal/swig/python/build/lib.linux-x86_64-2.4:/home/warmerda/mapserver/mapscript/python/build/lib.linux-x86_64-2.4

Frank,

Thanks, your trick works for me very well.

Cheers
-- 
Mateusz Loskot
http://mateusz.loskot.net