[GRASS-dev] Re: [GRASS GIS] #580: WinGRASS:
$GISBASE/etc/gui/scripts/ require something like $(EXE) to run
GRASS GIS
trac at osgeo.org
Fri Jan 6 09:56:20 EST 2012
#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:39 glynn]:
> Replying to [comment:34 mmetz]:
>
> > Reopening the ticket because calling python scripts from /scripts with
wxGUI does not work with the error message that the system does not know
what to do with py files. This applies to systems without a separate
system-wide python 2.x installation. Or is a separate python 2.x
installation now a requirement?
>
> The system must be able to "execute" Python scripts.
>
> On Unix, this means that a Python interpreter named "python" must be
present in $PATH. On Windows, it means that a Python interpreter must be
associated with the .py extension.
That means that some python 2.x must be installed system-wide. The
wingrass installer does not install python (%GISBASE%\extrabin\python.exe)
system-wide and does not associate it with the .py extension (such as not
to break any existing system-wide python-installation).
Strangely, if I click on Cancel on the Windows window with the error
message that a py file can not be opened, it is opened successfully and
the corresponding GUI dialog appears. Obviously, that error message
appears again when running the script (click on Run), and the script
completes successfully after canceling the windows message.
BTW, this applies to the latest GRASS7 wingrass installer, r50073.
Markus M
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/580#comment:40>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list