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

[Moritz Lennert]

On 10/02/14 09:57, Markus Metz wrote:
> Glynn Clements wrote:
>> This is my entire point. But that cannot be achieved if you're relying
>> upon hard-coded special treatment for Python scripts. If Python
>> scripts cannot simply be executed (via system() or subprocess.Popen()
>> or whatever) in the same manner as executables or other scripts, the
>> user will have to be bothered with whether something is an executable
>> or a Python script.
>
> We use hard-coded special treatment for shell scripts and still they
> behave like a GRASS module. I don't see how users are bothered whether
> a module is an executable or a shell script. Internally, GRASS can
> always use system() or subprocess.Popen() for executables and .bat
> files, but not for shell or Python scripts, 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 ?

Moritz