[GRASS-dev] r54612 - grass/trunk/mswindows - wingrass: attempt to define python file association

[Martin Landa]

Hi,

2013/1/14 Glynn Clements <glynn at gclements.plus.com>:
>> > wingrass: attempt to define python file association
>>
>> any idea if this possibly interfere with a file association already set by
>> other python-installations e.g. from www.python.org?
>
> Yes; it should be reverted.

OK, in this case please suggest better solution. Currently after
installing GRASS on Windows, the python scripts (eg. r.reclass.area)
do not work. Usually after launching such command Windows ask the user
for application to use or simply open the script in the text editor.
It's bad.

> A GRASS installer should not attempt to install Python other than by
> (possibly) downloading and executing the appropriate installer from
> python.org.

Currently the native installer contains python which is provided
within osgeo4w framework (taken from python.org ASAR). Agreed, in
other words, do not install python if there is already other python
installed. Any idea how to implement in nsis installer?

> For wxGUI, it is sufficient to bundle a "private" Python installation
> and set the relevant environment variables in the GRASS startup (but
> it should be possible to disable this if the system Python is
> compatible with GRASS and wxGUI).

Problem are python scripts (like r.reclass.area), lunched from command
line or wxGUI command prompt.

> This won't work for general-purpose scripting. The only thing which
> *will* work is to have a suitable version of Python (plus any
> necessary packages) installed system-wide. And that isn't something
> which GRASS can do anything about, nor should it try (other than by
> providing advice to the user).

Hm, not sure. Esri ArcGIS contains also installation of Python. I
would assume that Windows user expect that everything is solved within
installation process.

Martin

-- 
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa