[GRASS-dev] Handling of Python scripts on MS Windows
wenzeslaus at gmail.com
Wed Oct 2 07:47:35 PDT 2013
Comparing to unix-like systems, MS Windows works strangely in terms of
executing programs (and scripts). Additionally, MS Windows don't have
package manager and packagers which would take care of incompatibilities
between applications. Moreover, most of the MS Windows applications behaves
in the way that they are the best and the only application on the system,
so they just associate every possible file with their programs (and
I'm always for pure, correct and clean solutions. However, I'm not expert
neither in MS Windows registry nor in Python virtual environments nor in
covering .py to .exe and nobody provided other implementation, so I
provided mine which is messy but it only reflects mess which I---maybe just
because of my lack of knowledge---see on that system.
I don't vote for my change to be permanent if we find a different solution.
But the fact is that scripts are not working now (for large number of
people) and this is the only solution we have. Like with democracy which
not perfect but it is the best political system available.
On Wed, Oct 2, 2013 at 7:16 AM, Glynn Clements <glynn at gclements.plus.com>wrote:
> Vaclav Petras wrote:
> > Anna and I have fixed the script handing on MS Windows. Modules which are
> > Python scripts and/or are from GRASS addons and/or calls other modules
> > which are Python scripts didn't worked for various reasons. The changeset
> > r57910 should fix them all (and thus should fix #2039, particularly the
> > MAXREPEAT error).
> Note that I've removed the hacks from core.py. So whatever bugs they
> were trying to work around will have to be fixed where they originate.
> Glynn Clements <glynn at gclements.plus.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev