[GRASS-dev] [GRASS GIS] #3508: grass start up: buggy to_text_string

[GRASS GIS]

#3508: grass start up: buggy to_text_string
--------------------------+-------------------------------
  Reporter:  martinl      |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  blocker      |  Milestone:  7.2.3
 Component:  Startup      |    Version:  svn-trunk
Resolution:               |   Keywords:  wingrass, unicode
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------------

Comment (by mlennert):

 I think this is a classical case of it being better not to mess around
 with the original byte string. All we do is taking a string from an
 environment variable, adding two new path elements and putting it back
 into another environment variable:

 {{{
 addon_base = os.getenv('GRASS_ADDON_BASE')
 [...]
 addons_man_path = os.path.join(addon_base, 'docs', 'man')
 os.environ['MANPATH'] = to_text_string(addons_man_path)
 }}}

 Do we really have to worry about encoding/decoding in that context ?

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