[GRASS-dev] Re: [GRASS GIS] #841: python script modules should use pythonw on OSX; they also ignore GRASS_PYTHON

[GRASS GIS]

#841: python script modules should use pythonw on OSX; they also ignore
GRASS_PYTHON
--------------------------+-------------------------------------------------
  Reporter:  kyngchaos    |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect       |      Status:  new                      
  Priority:  normal       |   Milestone:  6.5.0                    
 Component:  default      |     Version:  unspecified              
Resolution:               |    Keywords:                           
  Platform:  Unspecified  |         Cpu:  Unspecified              
--------------------------+-------------------------------------------------
Comment (by kyngchaos):

 Replying to [comment:1 glynn]:
 > Most 7.x scripts don't use wxPython directly. They might use it
 indirectly via g.parser, but that should be dealt with by $GRASS_PYTHON.

 OK.  I was going by the new v.krige in 6.5, where I noticed the problem.
 So, the g.parser stuff happens in a completely separate process?  What I
 saw in one module I looked at is that the script loads the grass module,
 then runs grass.parser(), then runs the main script.  No chance for it to
 run anything with GRASS_PYTHON.

 > No slash between "env" and "python".

 fingers acted on their own ;)

 > AFAICT, most scripts should be using "python", not "pythonw"

 Except when they use wx, like v.krige.

 >> Though, I see another potential problem with the #! -- it completely
 ignores GRASS_PYTHON,
 > That shouldn't be a problem.

 How is that not a problem?  Say there are 2 pythons in the PATH (or
 another not in the PATH) and I don't want to use the first one, so I set
 GRASS_PYTHON to the full path to the other.  But then /usr/bin/env
 python[w] goes and runs the first one anyways.

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