[GRASSGUI] initiating d.* command dialogs with existing parameters

[Jachym Cepicky]

Hi,

I agree, that Python 2.4 should be the minimum required. I have it on
my laptop too. The "problem" are computers on ITC-irst. We will have
to consult this with system administration..

So from my side: please, continue using python's 2.4 features

Jachym

2007/3/25, Glynn Clements <glynn at gclements.plus.com>:
>
> Michael Barton wrote:
>
> > I¹ve set up a  structure (in gisutils and menuform) to pass command
> > parameters from an existing layer in the GIS Manager to the options dialog
> > when it is opened. We still need to parse existing d.* command in
> gismutils
> > to do this (and of course debug in menuform). This will work much easier
> if
> > a command is created as a list instead of a string. Glynn suggested this,
> > but there were some questions/concerns from Jachym about using spawn. I¹ll
> > hold off on finishing this until we get it settled about parsing a command
> > as a string or list.
>
> Parsing or passing?
>
> If we're willing to accept a requirement of Python 2.4 or later, then
> it appears that the subprocess module (the Popen class and the call
> convenience function) is the preferred interface.
>
> It seems to cover all of the required cases, doesn't use a shell
> unless explicitly told to, and appears to implement all relevant
> functionality on both Unix and Windows.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
>
> _______________________________________________
> grassgui mailing list
> grassgui at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grassgui
>


-- 
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub