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

[Moritz Lennert]

On 13/04/14 20:33, Martin Landa wrote:
> 2014-04-13 17:03 GMT+02:00 Moritz Lennert <mlennert at club.worldonline.be>:
>> On 11/04/14 13:05, Martin Landa wrote:
>> I don't think this a very helpful attitude. This whole debate is not about
>> one bad guy keeping the rest of the good guys from moving forward. First of
>> all, Glynn is not alone in his position.
>
> nobody is saying anything about a bad gay, it's your feeling not mine
> I can say. The fact is that this debate started more than one year ago
> (probably two years ago or more) with *no* consensus or accepted
> *solution*. I was playing with virtualenv, python launcher. I will be
> more than satisfied if we find acceptable solution. We need to
> continue and focus our energy on other important topics or we just
> keep discussing this topic for other two or three years and blocking
> any of releases. If you find a better solution in the near future we
> can easily to integrate it and avoid current dirty workarounds. I am
> looking forward to see real-working-solid solution as the outcome of
> this debate. Till now I can hardy see it.

I believe, and that's what I've been trying to get at, that our problem 
is not finding the solution, but defining the problem.

If we want to build a more monolithic GRASSWin then some solutions are 
on the table, but they go against the aim of allowing to run GRASS as a 
library of tools which is available from everywhere, not only from 
within the monolithic tool. For this latter aim, some solutions are on 
the table, but they go against the aim of creating a one-click installer 
for GRASS which "just works" without any need for the user to understand 
issues of system-wide Python installation.

So, unless we decide which of these aims (i.e. problems) we make our 
priority, we will never be able to decide on a solution.

Moritz