[GRASS-dev] [GRASS GIS] #3565: Porting Python Scripting Library to Python 3

GRASS GIS trac at osgeo.org
Tue May 22 22:42:37 PDT 2018

#3565: Porting Python Scripting Library to Python 3
  Reporter:  annakrat     |      Owner:  grass-dev@…
      Type:  task         |     Status:  new
  Priority:  normal       |  Milestone:  8.0.0
 Component:  Python       |    Version:  svn-trunk
Resolution:               |   Keywords:  gsoc2018, python3
       CPU:  Unspecified  |   Platform:  All
Changes (by sanjeet):

 * Attachment "patch_core_run_command_unicode.diff" added.

 Hi, Here is a quick dirty patch to know if this is what you meant when you
 said we need to have 'encoding' parameter passed to our functions. For
 now, I have only added this conversion in the 'run_command()'. I am just
 using the encoding parameter directly from kwargs instead of passing it as
 a keyword argument in the functions definiton. It is being popped from the
 kwargs dictionary so as not to pass it to the next function in line. I
 thought, in the similar manner we could call the 'make_unicode()' in other
 functions (read_command, make_command, start_command,...) where they can
 make use of it if they are called directly from the scripts instead of
 other functions. Is this correct?

Ticket URL: <https://trac.osgeo.org/grass/ticket/3565>
GRASS GIS <https://grass.osgeo.org>

More information about the grass-dev mailing list