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

GRASS GIS trac at osgeo.org
Mon Oct 27 20:03:31 PDT 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 wenzeslaus):

 Replying to [comment:24 glynn]:
 > Replying to [comment:20 wenzeslaus]:
 > > This is a serious change which will require a lot of testing in both
 modules (core and addons) and GUI. What are the opinions on doing
 something like that?
 > The existing behaviour is wrong and should be fixed before 7.0 is
 > > The alternative is to go for 7.x and probably even further (8.x) with
 the current unsafe but broadly used API
 > The Python scripting API is new in 7.0, which hasn't been released yet.
 The fundamental feature of 7.0 was that we get to break compatibility for
 the sake of correctness, so it makes no sense break correctness for the
 sake of compatibility with something which hasn't even been released.

 I was working on #2326 a little bit last week but I'm far from finishing.
 I have a first implementation of raise in run/write/read command functions
 and some changes make GUI start again. Nothing done on the rest of the
 code. Patch `run_with_raise_core.diff` attached.

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

More information about the grass-dev mailing list