[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 zarch):

 Replying to [comment:1 mlennert]:
 > http://osgeo-org.1560.x6.nabble.com/Handling-of-Python-scripts-on-MS-
 Windows-tt5081335.html
 >
 > I would guess that this thread is probably one of the longest in grass-
 dev history. Have fun ! ;-)


 Thanks Moritz, I saw the thread but it seems to me that it is not going
 anywhere, so I'm trying to change prospective. I think that my point is
 close but it is not the same. I'm not talking on how to execute
 automatically the GRASS scripts on windows, I'm talking on choosing the
 default interpreter that must be used by GRASS.

 If I understood the long thread we were talking on how we can link the
 windows default python interpreter to run our scripts, if we have to use
 or not the default python interpreter. Instead here I'm talking to give to
 the user the chance of choosing which python interpreter must be used by
 GRASS, if not specify just use its own interpreter.

 The problem if choosing a different python interpreter could be the ctypes
 binding of python that must be re-compiled, isn't it?

 I don't want to use the default GRASS interpreter because I need other
 libraries that are not present on the GRASS python interpreter (GPyI) and
 install these libraries is not easy, generally they require to compile,
 and compile on windows is a pain.

 The solution that I found and it is working so far, it is just to copy all
 the python/site-packages from pythonxy to the site-packages of the GPyI.

 But it is just a work around, IMHO the best option should be to be able to
 choose during the installation process which one should be used by GRASS.

 Pietro

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