[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 11:27:32 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 martinl):
Replying to [comment:39 glynn]:
> 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.
>
> Please do not try to implement half-baked "fixes" such as requiring .bat
files or requiring special treatment for executing scripts. Both Unix and
Windows have standard mechanisms to support execution of scripts; those
mechanisms (and only those mechanisms) should be used.
just to sure what we want...
python scripts should be executable from
1. cmd
2. msys
3. wxGUI
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?
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/580#comment:41>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list