Check out all the Python gotchas commonly found in GDAL. Not all items listed here are bugs. Some of these are just how GDAL and OGR work and cannot be fixed easily without breaking existing code.
If you don’t like how something works and think it should be changed, feel free to discuss it on gdal-dev and see what can be done.
- Python bindings do not raise exceptions unless you explicitly call
- Python crashes if you use an object after deleting an object it has a relationship with
- Python crashes if you add a new field to an OGR layer when features deriving from this layer definition are still active
- Layers with attribute filters (
SetAttributeFilter()) will only return filtered features when using
- Certain objects contain a
Destroy()method, but you should never use it
- Saving and closing datasets/datasources
- Exceptions raised in custom error handlers do not get caught
- Gotchas fixed in GDAL 1.8.0
- Gotchas that result from bugs or behaviors of other software