Ith seems to be a "Python Path" issue. Python libraries are looked-up within a defined path. Try
import sys
sys.path
If the directory where the gdal.py and related files is not in this list, then Python cannot find it. That's for the "diagnostics" part. To fix the situation, you have several options... They all hinge on knowing the rules which Python uses to build this path.
- The PYTHONPATH environement variable can be altered to include the desired path
- Python can be started from the directory where the desired library resides.
- sys.path can be dynamically altered, with sys.path.append("/SomePath/To/MyStuff")
The only place where I've seen the rules pertaining to the building of sys.path formerly described, within the "official" Python documentation, is in the tutorial, at section 6.1.2
Excerpt:
modules are searched in the list of directories given by the variable sys.path
which is initialized from the directory containing the input script (or the
current directory), PYTHONPATH and the installation- dependent default. This
allows Python programs that know what they’re doing to modify or replace the
module search path. Note that because the directory containing the script being
run is on the search path, it is important that the script not have the same name
as a standard module, or Python will attempt to load the script as a module when
that module is imported. This will generally be an error. See section
Standard Modules for more information.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…