[GRASS-dev] making python scripts be part of GRASS

[Michael Barton]

Jachym,

This looks very useful. I'm looking forward to getting back to wxGRASS after
winding up GRASS 6.2/6.3 bug fixes.

I want to clarify this a bit for others.

This is a way to create a GRASS script (complete with the standard GUI
interface) in Python instead of bash.

Thanks much.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Jachym Cepicky <jachym.cepicky at centrum.cz>
> Date: Sat, 23 Sep 2006 17:08:33 +0200
> To: <grass-dev at grass.itc.it>
> Subject: [GRASS-dev] making python scripts be part of GRASS
> 
> hallo,
> 
> maybe, I just reinvent wheel, but this could be interesting for those of
> us, who would like to get GRASS-help and GRASS controll of input
> parameters to their python/perl/whaterver scripts.
> 
> Idea: use g.parser and then just read the environment variables.
> 
> example in attachment. should this file go to general/g.parser/test.py ?
> should I update man page to g.parser ? any improvements? would anybody
> prepare equivalent version for perl?
> 
> jachym
> -- 
> Jachym Cepicky
> e-mail: jachym.cepicky at centrum.cz
> URL: http://les-ejk.cz
> GPG: http://les-ejk.cz/gnupg_public_key/jachym_cepicky-gpg_public_key.asc
> -----------------------------------------
> OFFICE:          
> GDF-Hannover
> Mengendamm 16d
> 30177 Hannover
> Germany
> e-mail: cepicky at gdf-hannover.de
> URL:    http://gdf-hannover.de
> Tel.:   +49 511-39088507