Hi,

2010/10/30 Glynn Clements <[email protected]>:
> Beyond that, we should probably think about how to deal with errors in
> the Python scripting library. I.e. whether to raise Python exceptions,
> return status codes, call fatal(), etc. Right now, each function does
> as it pleases; there isn't any consistency.

r44086 helps a bit?

error() raise ScriptException() by default. If you call
raise_on_error(False) then error() prints error message via `g.message
-e`.

Martin

-- 
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to