[GRASS-dev] [GRASS GIS] #1832: Python scripts are with mixed tabs and spaces

[GRASS GIS]

#1832: Python scripts are with mixed tabs and spaces
-------------------------+--------------------------------------------------
 Reporter:  klo          |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.3                    
Component:  Python       |     Version:  unspecified              
 Keywords:               |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by wenzeslaus):

 The problem is that we use 4 spaces indentation which really does not fit
 with 8 spaces wide tabs. In my view, it causes confusion. Of course, you
 often realize where is the problem, but is it necessary? (The is similar
 for GRASS C code (#1663) but the problem for Python is more critical since
 we don't and cannot have auto-indent tool for Python.)

 Moreover, the problem of white spaces in GRASS Python code is larger. Try
 to use pep8 tool, the result is really bad. I think that if there is some
 standard, we should keep it, at least the basic rules.

 I understand the problem of editor settings. I encountered it, too.
 However, I also know the opposite problem. My Python editor is confused
 and complains about GRASS code and thus it is sometimes hard to use
 editor's code checking features.

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