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

GRASS GIS trac at osgeo.org
Mon Oct 5 20:09:24 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 glynn):

 Replying to [comment:10 cmbarton]:
 > So far nothing works. We did up the Python script the way it is
 suggested in the WIKI and it works fine on Linux and Mac. It either does
 nothing or hangs before launching on Windows. The farthest we've gotten is
 to get the error that the script does not generate an XML interface-
 description. My interpretation is that python parser work on Linux and Mac
 but not on Windows from the command line.

 On Windows, 6.4's g.parser explicitly invokes the script via $GRASS_SH.
 Obviously this won't work for Python scripts.

 FWIW, Python scripts work in Windows in 7.0, whether the script is in the
 path or not (once PYTHONPATH has been set; Init.bat doesn't set this).

 The biggest difference between the two is that in 7.0, the
 grass.script.parser() Python function uses "g.parser -s", which eliminates
 the need to re-execute the script. It may be worth back-porting this
 feature to 6.x (the existing behaviour is still available for use by shell

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

More information about the grass-dev mailing list