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

GRASS GIS trac at osgeo.org
Sat Jan 23 11:20:31 PST 2016


#2333: choose python interpreter during the GRASS installation on windows
-------------------------+-------------------------------------------------
  Reporter:  zarch       |      Owner:  grass-dev@…
      Type:              |     Status:  new
  enhancement            |
  Priority:  normal      |  Milestone:  7.1.0
 Component:  Python      |    Version:  svn-trunk
Resolution:              |   Keywords:  windows installer python
                         |  interpreter
       CPU:  All         |   Platform:  MSWindows 8
-------------------------+-------------------------------------------------

Comment (by hellik):

 Replying to [comment:24 annakrat]:
 > It seems Pietro got pretty close to solving this, any possibility we
 could restart the attempts? The patch may need a review by Helmut and then
 we can apply it to trunk? I would be glad to test it.

 the patch needs some review as the nsis-script changed a lot since then
 (e.g. 32bit/64bit, changes in env.bat, ...).

 there are some open questions:

 - should there in the standalone installer be only the option to choose
 the python interpreter or also some check of needed dependencies
 (wxwidgets, python win api etc.)? for example my system wide python
 installation (installed by another software) isn't compatible to run
 winGRASS out of the box

 - how/if should such an option implemented in OSGeo4W-winGRASS too? if
 not, there would be disparity between different platforms on windows
 (standalone, OSGeo4W, QGIS bundled). how should our users deal with these
 many different variants? e.g. for myself I never work with the standalone
 installer, prefer the OSGeo4W-environment as there are quite a lot tools,
 which can easily be updated.

 - ...

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



More information about the grass-dev mailing list