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

[Vaclav Petras]

On Sat, Apr 26, 2014 at 6:42 AM, Glynn Clements <glynn at gclements.plus.com>wrote:

> > >> It's easier to check if the file is a python script and if so than
> > >> to force to use bundled version of Python.
> > >
> > > So long as I have commit access, GRASS isn't going to be "forcing" the
> > > use of a non-system Python.
> >
> > But an existing system Python on MS Windows can change or disappear
> > any time, and a GRASS installation will not be notified about this
> > change.
>
> Yes; and your point is?
>
> If my system Python were to suddenly change or disappear, I'd be far
> more concerned about "who did that, and how?" than about GRASS not
> working.


Please consider this scenario:

1. user installs ArcGIS which installs Python system-wide
2. user installs GRASS GIS which will use system-wide Python
3. user is happy with free and open source GIS, so user uninstalls ArcGIS
4. GRASS does not work
5 a. user does not understand and returns to ArcGIS
5 b. user understands that GRASS depends on ArcGIS and returns to ArcGIS
5 c. user asks on mailing list and installs Python or re-installs GRASS
which would install Python system-wide (nice but how probable?)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140426/841051d0/attachment-0001.html>