[gdal-dev] Problem importing osgeo module in Python

Christopher Barker Chris.Barker at noaa.gov
Fri Aug 8 19:36:01 EDT 2008

Roger André wrote:
>     that shouldn't be required -- site-packages should be on your
>     sys.path already. Is your python in /export/lib64/python2.3 ? Do you
>     have more than one python?
> My Python is not in  /export/lib64/python2.3. 

> That's a useful trick, thanks.  My python install appears to be in:
>  /usr/lib64/python2.3

> Thanks for the help.  I did get this working by adding the gdal lib path 
> to ld.so.conf and running ldconfig.  Then added a PYTHONPATH setting in 
> .bashrc that points to the /export/lib64/site-package dir.

the question is: why did gdal put your python extensions there? Is there 
anything else there?

What is /export? I've seen that before.

Do you have a site-packages dir in /usr/lib64/python2.3 anywhere? Maybe 
you could put a link in /usr/lib/python2.3 to /export/lib64/site-packages

On the other hand, you have it working, so why mess with it?


Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov

More information about the gdal-dev mailing list