[GRASS-dev] Installing non-standard Python addons in winGRASS
wenzeslaus at gmail.com
Mon Jun 18 08:59:32 PDT 2018
On Mon, Jun 18, 2018, 5:19 AM Michel Wortmann <wortmann at pik-potsdam.de>
> I can give it a try but I don’t actually work on Windows myself,
Neither do I, hence the suggestion for the flag.
i.e. testing and developing this would be a bit cumbersome.
If you use as much as possible all different system abstractions, i.e., use
the standard Python library and read documentation, you should be able to
get quite far. Most of it will be platform independent (is my guess).
you are ok with testing it and fully implementing it in g.extension, then
> that would be great.
I hope there is enough people interested in this feature to test it on
Windows. I can do the code review unless someone else volunteers.
> On 15. Jun 2018, at 16:48, Vaclav Petras <wenzeslaus at gmail.com> wrote:
> On Fri, Jun 15, 2018 at 6:55 AM, Michel Wortmann <wortmann at pik-potsdam.de>
>> Any help would be greatly appreciated. I would also volunteer to test/add
>> a Python script installation function to g.extension, as hinted on in the
>> man page.
> For me, the preferred solution is to add that functionality to
> g.extension, i.e. re-implement the make/Makefile functionality in Python
> and then switch to that on MS Win (with a flag to do the same on other
> systems too). If you already have some code or you are willing to take a
> shot at this, please go ahead and open a ticket and submit a patch.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev