[GRASS-dev] g.message and unicode in python

Vaclav Petras wenzeslaus at gmail.com
Fri Nov 21 13:42:08 PST 2014

On Fri, Nov 21, 2014 at 1:46 PM, Nikos Alexandris <nik at nikosalexandris.net>

> So, it's bad idea even trying to do this (and thinking that everyone is
> going to read it)? Best practice to avoid such situations alltogether and
> respect the cross-platform principle?

It seems safer to me to print unicode characters using Python only and not
use g.message because for g.message you have to pass the characters to
another command. However, GRASS module message should go through g.message.
You should at least use stderr rather then stdout because stdout is in
GRASS reserved for the actual output of the modules.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20141121/7b3b74fa/attachment.html>

More information about the grass-dev mailing list