[gdal-dev] Error handlers in Python bindings

lpinner Luke.Pinner at environment.gov.au
Sat Jul 28 00:43:25 PDT 2012

>> The python function needs to accept three arguments, error class, error
>> and error message.
>> i.e.
>> from osgeo import gdal
>> def f(err_class, err_code, msg):
>>     print err_class, err_code, msg
>> gdal.PushErrorHandler(f)
>Reviewing the Python bindings code, I see no evidence that Python error
>are possible. An option is to use gdal.UseExceptions() which will cause a
>exception to be thrown after a GDAL call has emitted an error. 

Sorry for the late reply, I fired off my original reply without testing it
actually worked.  It seems this functionality is no longer available (maybe
with the change to the new style bindings?) or maybe it never worked in the
first place.  My original reply was based on a post from Frank on gdal-dev
_quite_ a few years ago -

View this message in context: http://osgeo-org.1560.n6.nabble.com/gdal-dev-Error-handlers-in-Python-bindings-tp4987591p4991515.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.

More information about the gdal-dev mailing list