(moving topic to grass-dev)
On Sun, May 23, 2010 at 10:15 PM, Hamish <hamish_b@yahoo.com> wrote:
Alex wrote:
GRASS 6.4 (Not sure why it's not final release yet)
a couple of outstanding issues off the top of my head,
- python scripts are not happy on WinGrass (apparently ok in 6.5, so selective backporting of code should fix this)
...
Where to look into that? Using "meld.sf.net", backporting is a snap.
Markus
Hamish:
> - python scripts are not happy on WinGrass (apparently
> ok in 6.5, so selective backporting of code should fix
> this)
...
Markus N:
Where to look into that?
the trick is knowing what needs backporting 
AFAIU Glynn's last comments on it stated that g.parser's -s flag had been
backported already but the grass.python library needed to be updated to
use it. Seems like an obvious place to start. (& see RelCrit trac ticket)
Michael seems to be at the coalface of encountering it. I'm not using
WinGrass or python scripts much in my work so just my understanding..
Hamish
Hamish wrote:
> > - python scripts are not happy on WinGrass (apparently
> > ok in 6.5, so selective backporting of code should fix
> > this)
> ...
Markus N:
> Where to look into that?the trick is knowing what needs backporting
AFAIU Glynn's last comments on it stated that g.parser's -s flag had been
backported already but the grass.python library needed to be updated to
use it.
That was the situation for RC6; the Python side has since been updated
in the 6.4 branch.
--
Glynn Clements <glynn@gclements.plus.com>