[GRASS-dev] [GRASS GIS] #2333: choose python interpreter during the GRASS installation on windows

[GRASS GIS]

#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 glynn):

 Replying to [comment:15 martinl]:

 > > If I interpreted correctly [0], the solution should be to generate the
 .bat files for each GRASS module/scripts written in python, right?.
 >
 > no, r60679 simply broke running all commands (ie. also running exe files
 from python), see the traceback from the previous comment.

 Ugh. So without shell=True it requires an explicit .exe suffix if the
 program has a dot in its name. And with shell=True, it interprets
 characters such as "|", "<", ">" and I don't know what else.

 So, do we mimic the shell (locate the program and determine its suffix),
 or use it (and determine the escaping rules so that "special" character
 get passed through to the underlying program correctly)?

 I still don't consider the previous approach (use the shell, don't bother
 escaping anything) to be a viable solution.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2333#comment:19>
GRASS GIS <http://grass.osgeo.org>