[GRASS-dev] Handling of Python scripts on MS Windows

[Vaclav Petras]

On Fri, Feb 7, 2014 at 11:49 AM, Glynn Clements <glynn at gclements.plus.com>wrote:

>
> Markus Neteler wrote:
>
> > > It's fairly trivial to set a valid GRASS environment globally, so that
> > > commands are usable in any shell. That's how I've had it on Linux
> > > since roughly forever; I don't run the grass70 script unless I'm
> > > testing it.
> > >
> > > FWIW, I want to make that the default mode of operation.
> >
> > Could you please elaborate? Say, what would be the difference to the
> > current way?
>
> The difference is that you don't "start" GRASS. You set the required
> environment variables from e.g. ~/.profile so that GRASS commands work
> in any shell (or via any other execution mechanism, e.g. M-! from
> within Emacs).
>
>
I'm still not sure if this is the best practice. I though I saw on mailing
list that somebody claimed that it is not safe. Not sure why, perhaps
because you are not getting the cleaning up procedures at the beginning and
at the end of GRASS session? Or how this is supposed to work with multiple
grass installations, which is a pretty common case?

Vaclav

> --
> Glynn Clements <glynn at gclements.plus.com>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140207/d8c42de8/attachment.html>