permail/gdal-dev/2003-March/000323.html
--
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.
___
gdal-dev ma
call has emitted an error.
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/gdal-dev-Error-handlers-in-Python-bindings-tp4987591p4987809.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
gdal-dev mailing list
hon bindings code, I see no evidence that Python error handlers
are possible. An option is to use gdal.UseExceptions() which will cause a Python
exception to be thrown after a GDAL call has emitted an error.
>
> --
> View this message in context:
>
http://osgeo-org.1560.n6.nabble.com/gda
print err_class, err_code, msg
gdal.PushErrorHandler(f)
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/gdal-dev-Error-handlers-in-Python-bindings-tp4987591p4987809.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
/gdal-dev-Error-handlers-in-Python-bindings-tp4987591p4987809.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Hey folks,
I'd like to know how I could set a custom error handling function in the
GDAL Python bindings?
Currently I was able to turn off error messages like so:
>>> gdal.PushErrorHandler("CPLQuietErrorHandler")
What I want is something like this:
>>> def f(error):
...logger.error(erro
