Open ninsbl opened 4 years ago
Uf. Yes, true. I remember I wanted to solve one issue somewhere and then push it to the official repository.
Well, as now I should also rewrite it to Python 3, maybe it's finally the right time to do that.
Issue #44 opened for the part of Python 3.
I remember I wanted to solve one issue somewhere and then push it to the official repository.
The blocking issue is #46. After solving that one, the modules could be made available in the official GRASS GIS AddOns repo.
Although there is still a lot of things to improve, I have solved all the blocking issues. Shall I move it to the official AddOns repository? How am I supposed to do it when there is a library needed for modules going into different directories (v.*
, r.*
, t.*
)?
Also, I think that I will keep a schizophrenic way of keeping this repo alive with all minor issues and proposals in parallel to the official GRASS AddOns repo. I hope it's fine, although not very systematic.
@ninsbl: Don't you use these modules in some processing chains to test everything? I have tested everything in a dummy manual way, but to be sure that something hidden didn't get broken.
Would be good to see those tools in https://github.com/OSGeo/grass-addons/tree/master/grass7
This may require some changes for Python 3?