[GRASS-dev] [GRASS GIS] #2326: Command functions in grass.script.core miss a correct error reporting

GRASS GIS trac at osgeo.org
Tue Nov 11 12:27:20 PST 2014


#2326: Command functions in grass.script.core miss a correct error reporting
--------------------------------+-------------------------------------------
 Reporter:  wenzeslaus          |       Owner:  grass-dev@…              
     Type:  enhancement         |      Status:  new                      
 Priority:  major               |   Milestone:  7.1.0                    
Component:  Python              |     Version:  svn-trunk                
 Keywords:  script, exceptions  |    Platform:  All                      
      Cpu:  Unspecified         |  
--------------------------------+-------------------------------------------

Comment(by neteler):

 Replying to [comment:36 wenzeslaus]:
 > Yes, it might be confusing. C API has `G_fatal_error()` and Python API
 has `error()` and `fatal()`. I've tried to improve the documentation in
 trunk in r62709.

 THanks but why do we need `error()` at all? If a function does not end the
 execution of the program it should be called warning... (which we have as
 well).

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2326#comment:37>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list