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

[GRASS GIS]

#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run
---------------------------+------------------------------------------------
  Reporter:  hamish        |       Owner:  grass-dev@…              
      Type:  defect        |      Status:  reopened                 
  Priority:  blocker       |   Milestone:  7.0.0                    
 Component:  wxGUI         |     Version:  svn-trunk                
Resolution:                |    Keywords:  wingrass                 
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------

Comment(by mmetz):

 Replying to [comment:50 glynn]:
 > Replying to [comment:43 mmetz]:
 > > WinGRASS is currently compiled against osgeo4w python and related
 packages,
 >
 > WinGRASS isn't "compiled" against any version of Python.

 OK, but GRASS is compiled "with" a particular Python version, for ctypes.
 And apparently wxversion is needed which is only available in a devel
 package (Linux).
 >
 > > > Adding .PY to the PATHEXT environment variable allows Python scripts
 to be run without the extension (in the same way as .bat, .cmd, etc). That
 will work for anything which uses the shell (system(), Python's subprocess
 module, batch files, etc).
 > >
 > > Even if the system knows nothing about any python.exe?
 >
 > If the .py extension hasn't been associated with a Python interpreter,
 executing Python scripts won't work, with or with the .py extension.
 >
 > If we don't want to spend the rest of our lives adding one hack after
 another to deal with Python scripts on Windows, "executing" a Python
 script (via !CreateProcess(), system(), subprocess.Popen() or whatever)
 has to just work, which requires that the .py extension is associated with
 a working Python interpreter.

 Should the existence of a working Python interpreter thus be the
 responsibility of the user? Should we therefore remove the bundled python
 from the wingrass installer? Because we do not want to interfere with an
 existing Python installation, we either do not include an official Python
 installer, or we do, but check first if any Python is already installed on
 the system.

 According to Helmut's report [comment:48] on the registry settings, I can
 not see any trace of the Python versions coming with Inkscape and
 !LibreOffice, but only of the Python version coming with ArcGIS.

 To phrase it provocatively, do we want to go the ESRI way or do we want to
 go the Inkscape and !LibreOffice way?

 Markus M

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