[GRASS-dev] Using grass.message in Python: Why does G_message() print to stderr and not stdout?

[Vaclav Petras]

On Sun, Sep 9, 2018 at 4:47 PM Markus Neteler <neteler at osgeo.org> wrote:
>
>
> > That gives little too much information, so perhaps:
> >
> > FILE="`./bin.x86_64-pc-linux-gnu/grass77 --tmp-location XY --exec which
r.mask`"
> > grass --tmp-location XY --exec python -m trace --trace $FILE -r | grep
`basename $FILE`
> >
> > Or do you want GRASS parser to print every module being executed?
>
> Yes, just the sequence of commands along with the parameter/flags
> used. Like "shell history" style. This would help for a quick
> orientation in long Python scripts with functions etc.

This sounds like a good enhancement for the parser. Ticket?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20180909/d2cc87b6/attachment.html>