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

[Markus Metz]

On Mon, Feb 10, 2014 at 12:04 PM, Moritz Lennert
<mlennert at club.worldonline.be> wrote:
> On 10/02/14 11:46, Markus Metz wrote:
>>
>> On Mon, Feb 10, 2014 at 11:26 AM, Helmut Kudrnovsky <hellik at web.de> wrote:
>>>>>
>>>>> Therefore we need
>>>>> hard-coded special treatment for shell and Python scripts in order to
>>>>> make sure that the correct interpreter is used.
>>>
>>>
>>>> Just for my understanding: When you say hard-coded special treatment for
>>>> shell scripts, are you speaking about the .bat files ?
>>>
>>>
>>> I think yes.
>>
>>
>> Or more generally, any mechanism explicitly using %GRASS_PYTHON%
>> script.py.
>
>
> But as far as I've seen, this might not be sufficient since this only
> indicates which Python executable to use for launching the Python script,
> but any library calls linked to that execution will involve the system-wide
> installed Python. Which is different from bash scripts, where this is not an
> issue.

GRASS Python scripts are currently executed using the system-wide
installed Python if it exists. No attempt has been made to explicitly
use GRASS_PYTHON, therefore it is not possible to say if the system's
Python would really be completely ignored.