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

[Markus Neteler]

On Wed, Feb 5, 2014 at 5:19 PM, Glynn Clements <glynn at gclements.plus.com> 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?

> I.e. on Unix, set the environment variables in /etc/profile.d/grass7
> or whatever a given distribution uses, so that you only need to
> explicitly start GRASS sessions if you want multiple, independent
> sessions.
>
> On Windows, GISBASE should be set from the registry (with the
> environment variables allowing this to be overriden, mainly as a
> developer feature).

Not sure what this would mean to the average user...

thanks for some more insights,
Markus