[GRASS-dev] Re: [GRASS GIS] #580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run

GRASS GIS trac at osgeo.org
Sat Oct 3 20:04:40 EDT 2009

#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run
  Reporter:  hamish        |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect        |      Status:  new                      
  Priority:  blocker       |   Milestone:  6.4.0                    
 Component:  wxGUI         |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:  wingrass                 
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
Comment (by hamish):

 Replying to [comment:7 cmbarton]:
 > Given all this, is there a way to run a Python script in GRASS for
 > Windows now (i.e., by including some code in the script or its
 > batch file) or will it have to wait until the GRASS code is
 > changed?

 I think the answer is yes, there is a way. This bug report is mostly
 worried about add-on scripts in $GISBASE/etc/gui/scripts being called from
 the GUI. You will have to experiment from the command line to test local
 g.parser scripts or those in GRASS_ADDON_DIR; please let us know results!


Ticket URL: <https://trac.osgeo.org/grass/ticket/580#comment:9>
GRASS GIS <http://grass.osgeo.org>

More information about the grass-dev mailing list