Hi dev team,
What is the latest on the g.extension known issue (quoting the man page):
"On MS-Windows, only the official repository is working because there is no way of compiling the modules (a Python replacement for Python scripts should be implemented).”
I have come to appreciate g.extensions url argument to install my own Python addons (local or from GitHub), but when I share them with Windows users, they have difficulties installing them. What is the recommended method to install them on Windows? My add hoc solution would be to write a little install.py script that moves the scripts and docs to the relevant GRASS_ADDON_BASE locations and create the .batch files in bin. But that seems hacky.
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.
On Fri, Jun 15, 2018 at 6:55 AM, Michel Wortmann <wortmann@pik-potsdam.de>
wrote:
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.
Hi Vaclav,
I can give it a try but I don’t actually work on Windows myself, i.e. testing and developing this would be a bit cumbersome. If you are ok with testing it and fully implementing it in g.extension, then that would be great.
Regards,
Michel
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.
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).
If
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.
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.