[GRASS-dev] [GRASS GIS] #2409: last call for options keys consolidation

[GRASS GIS]

#2409: last call for options keys consolidation
----------------------------------+-----------------------------------------
 Reporter:  martinl               |       Owner:  grass-dev@…              
     Type:  task                  |      Status:  new                      
 Priority:  blocker               |   Milestone:  7.0.0                    
Component:  Default               |     Version:  unspecified              
 Keywords:  standardized options  |    Platform:  Unspecified              
      Cpu:  Unspecified           |  
----------------------------------+-----------------------------------------

Comment(by martinl):

 Replying to [comment:102 wenzeslaus]:

 > For example, there will be no need to change `grass.script.raster3d`
 (which would end up as `grass.script._3draster` in the other case). From
 this point of view `raster_3d` is also not good because underscore should
 not be in the name of a Python module if possible and moreover I don't
 like `raster_3d` in general. Shortening possibilities are not as important
 to me as name without underscore.
 >
 > What about the module names? Are we changing that? Or is `raster3d` just
 `rast3d` in module names?

 Personally I would tend to rename just

  * element name `raster_3d` (or `raster3d`)
  * module options e.g. `d.legend raster_3d`

 I would not touch names of the modules, some of them already use shorten
 names, eg. `d.rast.leg`, so I would keep `rast3d`. Similarly I would not
 touch python module names.

 Any opinion from other devs?

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