[GRASS-dev] Python handling in winGRASS7 [was: Re: GRASS GIS 7 tech-preview release preparations]

[Moritz Lennert]

On 26/07/13 11:40, Helmut Kudrnovsky wrote:
> hi,
>
>
> On 26/07/13 00:04, Helmut Kudrnovsky wrote:
> [...]
>> Would it be a possible option to implement only a)
>
> there is already a bundled/embedded python in standalone WinGRASS6/7 and
> OSGeo4w-WinGRASS6/7.

Yes, so this should be reformulated as "keep the current option of 
bundling an embedded python".

However, again within the limits of my understanding, aren't the issues of

- calling a script from a script

and

- making addons easily callable

linked to the question of system-wide vs embedded Python ?

IIUC, in order to solve (at least) the first issue, you have to make 
python code callable and executable without the .py extension, using

assoc .py=Python.File
and
ftype Python.File=C:\Path\to\pythonw.exe "%1" %*

but as the ftype setting is system wide, you can't just hijack all 
python scripts on a machine to use the Python interpreter embedded in GRASS;

I'm really not expert enough on these issues, so some input from the 
gurus would help, here.

>
> some more issues related to WinGRASS and python are mentioned also in
>
> http://trac.osgeo.org/grass/ticket/2015

I didn't see this yesterday while experimenting with a fresh install on 
WinXP without system-wide Python installed. I'll try again with a 
system-wide Python installed to see if that makes any difference.


Moritz