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

[Benjamin Ducke]

Hi there,

On 04/02/14 13:24, Moritz Lennert wrote:
> On 04/02/14 11:29, Glynn Clements wrote:
>>
>> Markus Metz wrote:
>>> I agree. It seems that the wxGUI always uses the bundled GRASS_PYTHON,
>>> the reason why the wxGUI works fine without a system-wide Python.
>>
>> That was done so that the system Python doesn't need to have wxPython
>> installed. Note that wxpyimgview does something similar: the top-level
>> script invokes the wxPython program via GRASS_PYTHON explicitly.
>>
>> But this only works for a closed system which knows what it is
>> executing. It doesn't help us provide a command-line environment where
>> Python scripts just work as they should.
> 
> I think this is the basis of some of the frustration in the ongoing
> discussion: different use-cases and philosophies about what GRASS is and
> should be. I understand that for many users (and I would guess for part
> of the developers), GRASS _is_ a monolithic system and Python scripts
> are only used from within, but for others the fact that it is a more
> open, modular system makes for a large part of its attractiveness. So,
> the solution we have to find has to cater to both, and unfortunately,
> embedding Python will not suffice for the second use case.
> 

That's a really important point! GRASS is an example of
the Unix tradition of modular design. It owed and continues
to owe much of its flexibility to this fact. From my
point of view, its clean, modular architecture is also what
has given GRASS its amazing lifespan and maintainability.

The GUI design should never compromise that. In fact,
I believe the GUI is a matter of choice/taste and
should be exchangeable at will. We have GRASS running
as a processing backend for WPS and for several "host"
desktop GIS (QGIS, OpenJUMP, Kosmo, uDig, gvSIG, ...).

E.g., I use GRASS exclusively either through the command
line or via the GRASS plug-in in gvSIG CE. But with the
latest Python developments, it will be a real challenge to
integrate GRASS 7 in the same way that we could integrate
GRASS 6 into a "host" application (i.e. without messing
around with any system settings).

Best,

Ben

> I do have the feeling, though, that the python launcher is an
> interesting path to explore.
> 
> Moritz
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev



-- 
Dr. Benjamin Ducke, M.A.
{*} Geospatial Consultant
{*} GIS Developer

  benducke at fastmail.fm