[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 glynn):

 Replying to [comment:77 annakrat]:
 > Replying to [comment:76 cmbarton]:
 > > Could it cause a problem somewhere down the line to have this term
 beginning with a number--e.g. If it is used to name a temp file or
 something?
 >
 > As I already said, it causes problems for Python because keyword
 parameter can't start with number. This is solvable by adding underscore
 and some special handling of this case, which is partially there already.
 It violates pep8.

 PEP8 is a style guide. There is no inherent reason why an argument name
 cannot start with an underscore. And we're not even talking about explicit
 arguments; such arguments will only ever be obtained via the **kwargs
 mechanism.

 In fact, I think that this is why I chose to use a leading underscore
 rather than a trailing underscore.

 Still, I'd rather avoid having option names start with a digit. But unless
 we relax the ambiguity check, it wouldn't outweigh my preference to avoid
 using an option name which has a very common option name (rast or raster)
 as a prefix.

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