[GRASS-dev] [GRASS GIS] #2230: 'g.region -p' writes new WIND file, causes race condition for parallel jobs

[GRASS GIS]

#2230: 'g.region -p' writes new WIND file, causes race condition for parallel jobs
----------------------+-----------------------------------------------------
 Reporter:  hamish    |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  normal    |   Milestone:  6.4.4                    
Component:  Default   |     Version:  svn-develbranch6         
 Keywords:  g.region  |    Platform:  Linux                    
      Cpu:  x86-64    |  
----------------------+-----------------------------------------------------

Comment(by wenzeslaus):

 So, looking at r59383, r59386, r59387 and r59391, what is the set of
 `g.region` flags which should be used by default when scripting. If the
 region (WIND file) cannot be changed by default, why `g.region` is
 changing it? If the region (WIND file) needs to be changed by default, we
 should put a big warning to documentation about scripting (which can be
 always parallelized).

 > I think that the issue is essentially that people don't realise that
 g.region always sets the region unless -u is given.

 Again, as in previous paragraph, this is a documentation issue. This is
 not expected behavior and it is not properly documented.

 Also I don't understand why it is necessary to write the WIND file in
 `g.region` if the content was not changed.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2230#comment:3>
GRASS GIS <http://grass.osgeo.org>