235 | | * If you still want to use the GDAL Python API for your own applications, then use either of the following mutually exclusive configuration flags: |
236 | | * {{{--with-python}}}: the deprecated, but stable API. |
237 | | * {{{--ng-python}}}: the "next-generation" SWIG-based bindings, but may be problematic for some users (''e.g.'', Python 2.5 platforms). |
| 235 | * If you still want to use the GDAL Python API for your own applications, then the following configuration flags: |
| 236 | * {{{--with-python}}} {{{--without-ngpython}}}: the deprecated, but stable API. |
| 237 | * {{{--without-python}}} {{{--with-ngpython}}}: the "next-generation" SWIG-based bindings -- used to problematic for Python 2.5 users, but the GDAL team has solved a lot of these issues in 1.4.2. |
| 238 | * ''See generally'' [http://trac.osgeo.org/gdal/wiki/GdalOgrInPython GDAL/OGR In Python] on the GDAL trac wiki. |