[GRASS-user] problem using grass.write_comman, db.execute

[Nikos Alexandris]

On Thu, 2009-10-01 at 21:00 -0700, Hamish wrote:
> Nikos wrote:
> > grass.write_command('db.execute', input = '-', stdin = sql_coi_percent,
> > database = database, driver = driver)
> > -: No such file or directory
> 
> 'db.execute input=-' for stdin only works in grass7. for 6.4+6.5 it is
> simpler, just omit the input option all together.

Hmm... ok, thank you.

Scripting (or better said learning how to) can be very exciting but
changes (like the above) that break stuff are tough and can be
frustrating.

I read the other day that Python3 will introduce some changes. At what
extent will be os-geo stuff, and especially grass, affected? How should
an average scripter behave? How to prepare scripts that are ready for
changes?

Greets, Nikos