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

[Anna Petrášová]

On Tue, Jan 28, 2014 at 2:57 PM, Markus Metz
<markus.metz.giswork at gmail.com>wrote:

> Trying a summary on this discussion.
>
> AFAIU, the whole discussion boils down to the question if we want to
> require a system-wide installation of Python with correct python file
> associations in the registry, potentially deactivating an existing
> Python installation, or not.
>
> There seems to be agreement that we do not want to modify any existing
> system-wide python installation.
>
> That means that WinGRASS should
> 1) not do a system-wide installation of Python
> 2) not require a system-wide Python installation
> 3) explicitly ignore any existing system-wide installation of Python,
> or any Python file associations in the registry (text-editor,
> whatever)
>
> That means that we must assume that Windows has no idea what to do
> with Python files, and if it has an idea, this is most probably a bad
> idea, as far as GRASS scripts are concerned. As for shell scripts in
> GRASS 6. That in turn means that GRASS Python scripts must be called
> explicitly with GRASS_PYTHON, most importantly scripts from within
> scripts.
>
> IMHO, creating .bat files for python scripts is easy because the
> equivalent is already working for WinGRASS 6.4 where .bat files are
> created for shell scripts. AFAICT none of the other suggestions
> (virtualenv, Python launcher, pip, etc) has been tested successfully
> on Windows with GRASS 7, both with and without a separate incompatible
> system-wide Python installation.
>

Thanks for the summary.

About the bat files: I just realized I cannot run v.colors on Windows in
grass 6.4.4svn because v.colors is a bash script and inside it calls
another bash script (v.db.addcol) and it can't find it. I saw some pretty
old discussion on this topic [1]. I will create a ticket (I couldn't find
any). I am not sure if this is related to what you are suggesting but I
would like to mention it before we decide to go with bat files.

Anna

[1] http://lists.osgeo.org/pipermail/grass-user/2010-November/058654.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140128/1973c759/attachment.html>