[GRASS-dev] [GRASS GIS] #1941: wxGUI fails with Japanese locale

[GRASS GIS]

#1941: wxGUI fails with Japanese locale
----------------------+-----------------------------------------------------
 Reporter:  venkat    |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  blocker   |   Milestone:  7.0.0                    
Component:  wxGUI     |     Version:  svn-trunk                
 Keywords:  wingrass  |    Platform:  MSWindows 7              
      Cpu:  x86-32    |  
----------------------+-----------------------------------------------------

Comment(by martinl):

 Replying to [comment:18 glynn]:
 > Replying to [comment:17 martinl]:
 >
 > > Usually it's caused by Python installed together with Esri ArcGIS. The
 newest version of ArcGIS 10.2 still comes with Python 2.7.3. It would be
 good to find solution on our side without overwriting system-installed
 Python.
 >
 > 2.7.3 should be fine for GRASS, right? So the solution should be to
 detect that the

 No, the problem still remains. Note that we have this problem only with
 standalone installer not with osgeo4w installer.

 > "system" Python is sufficient and not try to use the bundled Python
 (i.e. don't set PYTHONHOME, set GRASS_PYTHON to point to the system
 version, etc).

 But then we will have problem with other python packages (GRASS
 dependecies) which are installed through osgeo4w environment as `python-
 matplotlib` or `python-numpy`, right? Version of "system" python will be
 most probably different from the python version available in osgeo4w
 environment.

 > AFAICT, the issue is that the system python27.dll (from
 `Windows/System32` or `Windows/SysWOW64`) is being used, but PYTHONHOME
 points to the bundled version of the Python standard library.
 >
 > If you can start a Python shell using the GRASS Python, you can use
 [http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Process
 Explorer] to view the list of DLLs which are actually being used by that
 process. AFAIK, System32/SysWOW64 take precedence over everything except
 the directory containing the exe, and %PATH% comes last.

 Strangely `C:\Program Files (x86)\GRASS GIS 7.0.svn\extrabin\python.exe`
 launches python 2.7.3 (same as system python from `C:\Python27\ArcGIS
 10.2`)! When launching `C:\osgeo4w\bin\python.exe` I got expected version
 of python, so 2.7.4 (current osgeo4w python version). This partly explains
 the fact that we have this problem only with standalone installer.

 > [http://msdn.microsoft.com/en-
 us/library/windows/desktop/ms682586%28v=vs.85%29.aspx DLL Search Order].

 Right, when I launch `python.exe` which comes with standalone installer it
 points to `C:Windows\SysWOW64\python27.dll`. When I launch `python.exe`
 from `C:\OSGeo4W\bin` it points to the right dll file, ie.
 `C:\OSGeo4W\bin\python27.dll`.

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