[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@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:  6.4.0
Component:  wxGUI| Version:  6.4.0 RCs
 Keywords:  wingrass |Platform:  MSWindows XP 
  Cpu:  Unspecified  |  
-+--
 Hi,

 None of the GUI wrapper scripts called from the GUI menus work in WinGRASS
 due to lack of associated file extensions.

 these are the shell and python scripts installed in
 $GISBASE/etc/gui/scripts/

 explained here:
  http://thread.gmane.org/gmane.comp.gis.grass.devel/32133

 see also bug #234.


 Hamish

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 wenzeslaus):

 See also:
  * #2150 Cannot call Python scripts from Python on MS Windows (possible
 duplicate)
  * #2138 winGRASS6.4.svn - addon python script status?
  * [http://lists.osgeo.org/pipermail/grass-dev/2013-October/065896.html
 Handling of Python scripts on MS Windows]
  * [http://lists.osgeo.org/pipermail/grass-dev/2014-February/067373.html
 Handling of Python scripts on MS Windows] (question how QGIS OSGeo4W
 works)

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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:42 glynn]:
 > Replying to [comment:41 martinl]:
 >
 > > just to sure what we want...
 > >
 > > python scripts should be executable from
 > >
 > >  1. cmd
 > >  2. msys
 > >  3. wxGUI
 >
 > In 7.0, MSys isn't required, and supporting it shouldn't be GRASS'
 responsibility (I don't know of any other Windows application which goes
 out of its way to support being used from MSys). If it is supported, it
 shouldn't be at the expense of native operation.
 >
 > > without need to define extension, eg.
 > >
 > {{{
 > g.manual
 > }}}
 > >
 > > should be possible to execute somehow. But AFAIU, in this case Windows
 doesn't know that python should be called, right?
 >
 > No, Windows supports this. Installing Python associates the .py
 extension with the Python interpreter.

 WinGRASS does not install python, nor numpy, scipy, or wxpython. These are
 all bundled with wingrass but not installed the Windows way. Therefore the
 system does not know that there is something like python.exe and the
 system does not know what to do with .py files. IIRC, a decision was made
 some time ago to not install python the Windows way together with wingrass
 because that could interfere with already installed python versions.

 WinGRASS is currently compiled against osgeo4w python and related
 packages, i.e. msys packages. It looks like that either wingrass installes
 python system-wide, the Windows way, or wingrass does not require a
 system-wide python and uses its own python, but then some .bat wrapper
 like

 {{{
 @"%GRASS_PYTHON%" "%GISBASE%/scripts/g.manual.py" %*
 }}}

 (see [comment:35 martinl]) would be needed. Is there another solution for
 the case that wingrass should work without a system-wide python?


 > 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?

 BTW, there is another strange side-effect. Addon scripts for GRASS 7 do
 not execute. Because of a some ugly hack it is possible to get the GUI for
 an addon script (--interface-description works), but clicking on run
 returns an error that the module is not found. This happens on some, not
 all windows systems.

 Markus M

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 hellik):

 Replying to [comment:43 mmetz]:
 >IIRC, a decision was made some time ago to not install python the Windows
 way together with wingrass because that could interfere with already
 installed python versions.

 how do other software deal with this python issue?

 just a little overview here on my win7-box. python is shipped/bundled a
 few times:

 C:\Python26\ArcGIS10.0
 C:\Program Files (x86)\GRASS GIS 6.4.3svn\Python27
 C:\Program Files (x86)\Inkscape\python
 C:\Program Files (x86)\LibreOffice 3.5\program\python-core-2.6.1
 C:\Program Files\GIMP 2\Python
 C:\OSGeo4W\apps\Python27

 Helmut

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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:44 hellik]:
 > Replying to [comment:43 mmetz]:
 > >IIRC, a decision was made some time ago to not install python the
 Windows way together with wingrass because that could interfere with
 already installed python versions.
 >
 > how do other software deal with this python issue?
 >
 Maybe there are different approaches.

 > just a little overview here on my win7-box. python is shipped/bundled a
 few times:
 >
 > C:\Python26\ArcGIS10.0
 > C:\Program Files (x86)\GRASS GIS 6.4.3svn\Python27
 > C:\Program Files (x86)\Inkscape\python
 > C:\Program Files (x86)\LibreOffice 3.5\program\python-core-2.6.1
 > C:\Program Files\GIMP 2\Python
 > C:\OSGeo4W\apps\Python27
 >

 Which ones are known to the system? You can check in Systemsteuerung ->
 Software or similar. Maybe only the one of ArcGIS10?

 Markus M

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 hellik):

 Replying to [comment:45 mmetz]:
 > Which ones are known to the system? You can check in Systemsteuerung ->
 Software or similar. Maybe only the one of ArcGIS10?

 {{{
 C:\Users\>echo %PATHEXT%
 .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
 }}}

 and a screenshot of standard software related to python added.

 Helmut

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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:46 hellik]:
 > Replying to [comment:45 mmetz]:
 > > Which ones are known to the system? You can check in Systemsteuerung
 -> Software or similar. Maybe only the one of ArcGIS10?
 >
 {{{
 C:\Users\>echo %PATHEXT%
 .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
 }}}
 >
 > and a screenshot of standard software related to python added.

 I was rather interested about how many different python versions are in
 the list of installed software as known by the system. The list .py* file
 extensions does not give the full path to the python.exe being used, i.e.
 which one of the 6 python.exe's on your system will be used.

 Markus M

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 hellik):

 Replying to [comment:47 mmetz]:
 > I was rather interested about how many different python versions are in
 the list of installed software as known by the system. The list .py* file
 extensions does not give the full path to the python.exe being used, i.e.
 which one of the 6 python.exe's on your system will be used.

 it's not so easy to find out this in the strange windows world ;o), but
 here we go (it's in the registry):

 {{{
 Windows Registry Editor Version 5.00

 [HKEY_CLASSES_ROOT\py_auto_file]
 @=""

 [HKEY_CLASSES_ROOT\py_auto_file\shell]

 [HKEY_CLASSES_ROOT\py_auto_file\shell\open]

 [HKEY_CLASSES_ROOT\py_auto_file\shell\open\command]
 @="\"C:\\Program Files (x86)\\GRASS 6.5.SVN\\extrabin\\python.exe\"
 \"%1\""
 }}}


 {{{
 Windows Registry Editor Version 5.00

 [HKEY_CLASSES_ROOT\Python.CompiledFile]
 @="Compiled Python File"

 [HKEY_CLASSES_ROOT\Python.CompiledFile\DefaultIcon]
 @="C:\\Python26\\ArcGIS10.0\\DLLs\\pyc.ico"

 [HKEY_CLASSES_ROOT\Python.CompiledFile\shell]

 [HKEY_CLASSES_ROOT\Python.CompiledFile\shell\open]

 [HKEY_CLASSES_ROOT\Python.CompiledFile\shell\open\command]
 @="\"C:\\Python26\\ArcGIS10.0\\python.exe\" \"%1\" %*"

 [HKEY_CLASSES_ROOT\Python.CompiledFile\shellex]

 [HKEY_CLASSES_ROOT\Python.CompiledFile\shellex\DropHandler]
 @="{60254CA5-953B-11CF-8C96-00AA00B8708C}"
 }}}


 {{{
 Windows Registry Editor Version 5.00

 [HKEY_CLASSES_ROOT\Python.File]
 @="Python File"

 [HKEY_CLASSES_ROOT\Python.File\DefaultIcon]
 @="C:\\Python26\\ArcGIS10.0\\DLLs\\py.ico"

 [HKEY_CLASSES_ROOT\Python.File\shell]

 [HKEY_CLASSES_ROOT\Python.File\shell\Edit with IDLE]

 [HKEY_CLASSES_ROOT\Python.File\shell\Edit with IDLE\command]
 @="\"C:\\Python26\\ArcGIS10.0\\pythonw.exe\"
 \"C:\\Python26\\ArcGIS10.0\\Lib\\idlelib\\idle.pyw\" -n -e \"%1\""

 [HKEY_CLASSES_ROOT\Python.File\shell\open]

 [HKEY_CLASSES_ROOT\Python.File\shell\open\command]
 @="\"C:\\Python26\\ArcGIS10.0\\python.exe\" \"%1\" %*"

 [HKEY_CLASSES_ROOT\Python.File\shellex]

 [HKEY_CLASSES_ROOT\Python.File\shellex\DropHandler]
 @="{60254CA5-953B-11CF-8C96-00AA00B8708C}"
 }}}


 {{{
 Windows Registry Editor Version 5.00

 [HKEY_CLASSES_ROOT\Python.NoConFile]
 @="Python File (no console)"

 [HKEY_CLASSES_ROOT\Python.NoConFile\DefaultIcon]
 @="C:\\Python26\\ArcGIS10.0\\DLLs\\py.ico"

 [HKEY_CLASSES_ROOT\Python.NoConFile\shell]

 [HKEY_CLASSES_ROOT\Python.NoConFile\shell\Edit with IDLE]

 [HKEY_CLASSES_ROOT\Python.NoConFile\shell\Edit with IDLE\command]
 @="\"C:\\Python26\\ArcGIS10.0\\pythonw.exe\"
 \"C:\\Python26\\ArcGIS10.0\\Lib\\idlelib\\idle.pyw\" -n -e \"%1\""

 [HKEY_CLASSES_ROOT\Python.NoConFile\shell\open]

 [HKEY_CLASSES_ROOT\Python.NoConFile\shell\open\command]
 @="\"C:\\Python26\\ArcGIS10.0\\pythonw.exe\" \"%1\" %*"

 [HKEY_CLASSES_ROOT\Python.NoConFile\shellex]

 [HKEY_CLASSES_ROOT\Python.NoConFile\shellex\DropHandler]
 @="{60254CA5-953B-11CF-8C96-00AA00B8708C}"
 }}}

 Helmut

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 hellik):

 related http://trac.osgeo.org/grass/ticket/1282

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 glynn):

 Replying to [comment:43 mmetz]:

 > WinGRASS does not install python, nor numpy, scipy, or wxpython. These
 are all bundled with wingrass but not installed the Windows way. Therefore
 the system does not know that there is something like python.exe and the
 system does not know what to do with .py files. IIRC, a decision was made
 some time ago to not install python the Windows way together with wingrass
 because that could interfere with already installed python versions.

 Correct. WinGRASS should assume Python, the same way that it does on
 Linux. On Linux, we don't install Python, we just assume that
 "#!/usr/bin/env python" will invoke a suitable Python interpreter. Windows
 doesn't use a shebang, it uses extensions, so on Windows, the assumption
 should be that the .py extension is associated with a suitable Python
 interpreter.

 > WinGRASS is currently compiled against osgeo4w python and related
 packages,

 WinGRASS isn't "compiled" against any version of Python.

 > > 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.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 cmbarton):

 What has worked for the Mac is to bundle wxPython (that is where we've run
 into problems with versions) and use the system Python. We compile so that
 it works with both 2.6 and 2.7. I don't know if that would work for
 Windows or not, but maybe.

 Michael

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 glynn):

 Replying to [comment:51 mmetz]:

 > > WinGRASS isn't "compiled" against any version of Python.
 >
 > OK, but GRASS is compiled "with" a particular Python version, for
 ctypes.

 The ctypesgen program which generates the ctypes wrappers is a Python
 script. The generated ctypes wrappers don't depend upon the version of
 which Python was used to run ctypesgen.

 > And apparently wxversion is needed which is only available in a devel
 package (Linux).

 That would be a bug in the particular distribution. The Windows installers
 for wxPython include wxversion, and any sane Linux package for wxPython
 would do likewise. By separating wxversion from the main wxPython package,
 the distribution is effectively insisting that any wxPython-based code is
 customised for that specific distribution (i.e. is written for, and
 doesn't attempt to check for, that distribution's "official" wxPython
 version).

 > 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.

 The latter is preferable, but more work. I.e. if Python is not installed,
 we should attempt to install it (via official installers) and required
 packages. If Python is installed, we should check that it's a compatible
 version, and attempt to install any required packages (wxPython, numpy,
 etc) for that specific version.

 > 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.

 GUI "applications" don't require an installed Python. Typically, the
 Python interpreter is embedded in the application's main executable.
 Python scripts are only ever run from within that application. Often,
 scripts which are part of the application package wouldn't run elsewhere
 because they depend upon modules which are compiled into the application's
 executable.

 This doesn't work when we're trying to provide a command-line and/or
 scripting environment. Ultimately, people should be able to write scripts
 and run them e.g. from an icon on the desktop or from some other program
 which knows nothing about either GRASS or Python.

 (This depends in part upon fixing the installation process to make GRASS
 "sessions" an optional feature. I can't remember the last time I actually
 "started GRASS"; I just set up all of the environment variables in
 ~/.bash_profile so that GRASS commands work everywhere).

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

 ESRI way.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 hellik):

 Replying to [ticket:580 hamish]:
 > Hi,
 >
 > None of the GUI wrapper scripts called from the GUI menus work in
 WinGRASS due to lack of associated file extensions.
 >
 > these are the shell and python scripts installed in
 $GISBASE/etc/gui/scripts/
 >
 > explained here:
 >  http://thread.gmane.org/gmane.comp.gis.grass.devel/32133
 >
 > see also bug #234.
 >
 >
 > Hamish

 suggest to close the ticket as scripts are now working in winGRASS. at
 least downgrading priority if ticket should stay open.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 I wonder why this rule is not working

 {{{
 $(DSTDIR)/%.bat: $(MODULE_TOPDIR)/scripts/windows_launch.bat
 sed -e "s#SCRIPT_NAME#$(%)#" -e "s#SCRIPT_DIR#$(DSTDIR)#"
 $(MODULE_TOPDIR)/scripts/windows_launch.bat > $@
 unix2dos $@
 }}}

 it gives eg.

 {{{
 @"%GRASS_PYTHON%" "/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-
 mingw32/gui/scripts/.py" %*
 }}}

 should have been

 {{{
 @"%GRASS_PYTHON%" "/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-
 mingw32/gui/scripts/d.rast3d.py" %*
 }}}

 Similar variables like `$<` or `$@` works as expected.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:55 hellik]:
 > suggest to close the ticket as scripts are now working in winGRASS. at
 least downgrading priority if ticket should stay open.

 before that we need to fix makefiles to produce also bat files from
 `g.gui.*` modules and GUI scripts (see my comment above).

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 glynn):

 Replying to [comment:56 martinl]:

 > I wonder why this rule is not working
 >
 {{{
 $(DSTDIR)/%.bat: $(MODULE_TOPDIR)/scripts/windows_launch.bat
 sed -e "s#SCRIPT_NAME#$(%)#" -e "s#SCRIPT_DIR#$(DSTDIR)#"
 $(MODULE_TOPDIR)/scripts/windows_launch.bat > $@
 unix2dos $@
 }}}

 > Similar variables like `$<` or `$@` works as expected.

 What is "$(%)" supposed to be? The stem of a pattern rule (the part which
 matches the "%" in the target) is available via "$*".

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:58 glynn]:

 > What is "$(%)" supposed to be? The stem of a pattern rule (the part
 which matches the "%" in the target) is available via "$*".

 right, thanks, it helped, see r62955-6.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:57 martinl]:
 > Replying to [comment:55 hellik]:
 > > suggest to close the ticket as scripts are now working in winGRASS. at
 least downgrading priority if ticket should stay open.
 >
 > before that we need to fix makefiles to produce also bat files from
 `g.gui.*` modules and GUI scripts (see my comment above).

 done in r62956, but it's not working - attempt to launch `g.gui.animation`
 from cmdline:

 {{{
 C:\>Traceback (most recent call last):
   File "", line 1, in 
   File "C:\OSGEO4~1\apps\Python27\lib\multiprocessing\forking.py", line
 381, in
 main
 self = load(from_parent)
   File "C:\OSGEO4~1\apps\Python27\lib\pickle.py", line 1378, in load
 return Unpickler(file).load()
   File "C:\OSGEO4~1\apps\Python27\lib\pickle.py", line 858, in load
 dispatch[key](self)
   File "C:\OSGEO4~1\apps\Python27\lib\pickle.py", line 1090, in
 load_global
 klass = self.find_class(module, name)
   File "C:\OSGEO4~1\apps\Python27\lib\pickle.py", line 1124, in find_class
 __import__(module)
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\temporal\__init__.
 py", line 28, in 
 from temporal_algebra import *
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\temporal\temporal_
 algebra.py", line 450, in 
 import grass.pygrass.modules as pymod
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\modules\__
 init__.py", line 2, in 
 from grass.pygrass.modules.interface import Module,
 ParallelModuleQueue
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\modules\in
 terface\__init__.py", line 9, in 
 from grass.pygrass.modules.interface import module
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\modules\in
 terface\module.py", line 297, in 
 class Module(object):
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\modules\in
 terface\module.py", line 700, in Module
 @mdebug(1, extra=_get_bash)
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\modules\in
 terface\module.py", line 36, in mdebug
 msgr = get_msgr()
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\messages\_
 _init__.py", line 352, in get_msgr
 _instance[0] = Messenger(*args, **kwargs)
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\messages\_
 _init__.py", line 175, in __init__
 self.start_server()
   File
 "C:\OSGEO4~1\apps\grass\grass-7.1.svn\etc\python\grass\pygrass\messages\_
 _init__.py", line 185, in start_server
 self.server.start()
   File "C:\OSGEO4~1\apps\Python27\lib\multiprocessing\process.py", line
 130, in
 start
 self._popen = Popen(self)
   File "C:\OSGEO4~1\apps\Python27\lib\multiprocessing\forking.py", line
 258, in
 __init__
 cmd = get_command_line() + [rhandle]
   File "C:\OSGEO4~1\apps\Python27\lib\multiprocessing\forking.py", line
 358, in
 get_command_line
 is not going to be frozen to produce a Windows executable.''')
 RuntimeError:
 Attempt to start a new process before the current process
 has finished its bootstrapping phase.
 }}}

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:59 martinl]:

 > right, thanks, it helped, see r62955-6.

 r62055 produces for GUI scripts (`d.rast3d` and `d.wms`) the BAT files.
 But when adding a new 3D raster map to the GUI it seems that instead of
 BAT file is launched PY file. I removed PY from PATHEXT in r63160, but it
 had no effect. Is there any way how to force launching BAT wrappers
 instead of PY scripts? Or it must be placed in different directories?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:60 martinl]:

 > done in r62956, but it's not working - attempt to launch
 `g.gui.animation` from cmdline:

 this bug seems to be fixed in r63208

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:61 martinl]:

 > r62055 produces for GUI scripts (`d.rast3d` and `d.wms`) the BAT files.
 But when adding a new 3D raster map to the GUI it seems that instead of
 BAT file is launched PY file. I removed PY from PATHEXT in r63160, but it
 had no effect. Is there any way how to force launching BAT wrappers
 instead of PY scripts? Or it must be placed in different directories?

 any idea how to solve this issue?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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 martinl):

 Replying to [comment:63 martinl]:

 > > r62055 produces for GUI scripts (`d.rast3d` and `d.wms`) the BAT
 files. But when adding a new 3D raster map to the GUI it seems that
 instead of BAT file is launched PY file. I removed PY from PATHEXT in
 r63160, but it had no effect. Is there any way how to force launching BAT
 wrappers instead of PY scripts? Or it must be placed in different
 directories?
 >
 > any idea how to solve this issue?

 seems to be solved by r63592 (already backported to relbr70 as r63605).
 Since it's the last issue of this ticket I am taking liberty to close this
 ticket. Feel free to re-open if needed.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [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:  closed   
  Priority:  blocker   |   Milestone:  7.0.0
 Component:  wxGUI | Version:  svn-trunk
Resolution:  fixed |Keywords:  wingrass 
  Platform:  MSWindows XP  | Cpu:  Unspecified  
---+
Changes (by martinl):

  * status:  reopened => closed
  * resolution:  => fixed


-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev