[GRASS-dev] [GRASS GIS] #2039: Startup Error

[GRASS GIS]

#2039: Startup Error
------------------------------+---------------------------------------------
 Reporter:  akdeakin          |       Owner:  grass-dev@…              
     Type:  defect            |      Status:  new                      
 Priority:  normal            |   Milestone:  6.4.4                    
Component:  Startup           |     Version:  6.4.3 RCs                
 Keywords:  wingrass, python  |    Platform:  MSWindows 7              
      Cpu:  x86-64            |  
------------------------------+---------------------------------------------
Changes (by hamish):

  * keywords:  wingrass => wingrass, python


Comment:

 Hi,

 AFAIK we use `"$GRASS_PYTHON" "$SCRIPT.py"` everywhere now, and as long as
 we didn't miss any, so registry associations with other system Python
 installations shouldn't matter since python.exe is called with its full
 path. the trouble might be instead that the order of the PYTHONPATH is
 picking up the alternate install before the grass install. You might try
 editing the lines of the python code just before the traceback's line
 number and add a "print sys.path" to show the path order. Right now we are
 adding the grass paths to the end of that, may we need to be inserting
 them at the start of the list instead.

 so sys.path.append() -> sys.path.insert(1,) ?

 see also : http://stackoverflow.com/questions/10095037/why-use-sys-path-
 appendpath-instead-of-sys-path-insert1-path

 "`virtualenv` is a tool to create isolated Python environments."


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2039#comment:15>
GRASS GIS <http://grass.osgeo.org>