#2333: choose python interpreter during the GRASS installation on windows
--------------------------------------------------+-------------------------
Reporter: zarch | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.1.0
Component: Python | Version: svn-trunk
Keywords: windows installer python interpreter | Platform: MSWindows 8
Cpu: All |
--------------------------------------------------+-------------------------
Comment(by martinl):
Replying to [comment:19 glynn]:
> So, do we mimic the shell (locate the program and determine its suffix),
or use it (and
There was something similar installed for Python scripts (1). One option
would be to load all commands to an internal directory (similarly to
wxGUI) when loading python script library
{{{
{ 'bat': [], 'exe': ['g.parser', ...] }
}}}
rather then determining it's suffix for every command separately.
> I still don't consider the previous approach (use the shell, don't
bother escaping anything) to be a viable solution.
Using `shell=True` seems to be less problematic to me, is it problem to
determine escaping rules for special characters (I know only about pipe
problem till now).
(1)
http://trac.osgeo.org/grass/changeset/60679/grass/trunk/lib/python/script/core.py
(L56)
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2333#comment:20>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
