Python script fails on windows if parameter contains non-latin letters

[marisn]

I have written a python GRASS module that accepts string as an option (passed via parser). It runs just fine on Linux, but on Windows 10 it is causing failure:

gol name=ģļāžšķūņā ŗūķeļi steps=1000 density=0.25                               
Traceback (most recent call last):
  File ".\gol.py", line 233, in <module>
    options, flags = grass.parser()
  File "C:\OSGeo4W\apps\grass\grass-7.1.svn\etc\python\grass
\script\core.py", line 719, in parser
    cmdline += [b'"' + encode(arg) + b'"' for arg in
sys.argv[1:]]
  File "C:\OSGeo4W\apps\grass\grass-7.1.svn\etc\python\grass
\script\utils.py", line 174, in encode
    return string.encode(enc)
  File "C:\OSGeo4W\apps\Python27\lib\encodings\cp1257.py",
line 12, in encode
    return
codecs.charmap_encode(input,errors,encoding_table)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xec in
position 5: ordinal not in range(128)

The error seems to originate from the same place as for #2886

[marisn]

Info on version although the code seems to be the same also in trunk.

GRASS versija: 7.1.svn                                                          
GRASS SVN revision: 67699                                                       
Build date: 2016-01-29                                                          
Build platform: x86_64-w64-mingw32                                              
GDAL: 1.11.3                                                                    
PROJ.4: 4.9.2                                                                   
GEOS: 3.5.0                                                                     
SQLite: 3.7.17                                                                  
Python: 2.7.5                                                                   
wxPython: 2.8.12.1                                                              
Platform: Windows-8-6.2.9200 (OSGeo4W)

[glynn]

Replying to marisn:

I have written a python GRASS module that accepts string as an option (passed via parser). It runs just fine on Linux, but on Windows 10 it is causing failure:

I believe that this a consequence of releasebranch_7_2 incorporating r65804 but not r68927. I suggest backporting the latter.

[wenzeslaus]

r68927 backported in r69617.

[mlennert]

Has r69617 solved this issue ?

[neteler]

Ticket retargeted after milestone closed

[lucadelu]

Could this ticket be closed?

[martinl]

Ticket retargeted after milestone closed

[neteler]

No answer, assuming that the issue was solved with the changes done.