Python 3 upgrade needed

[awickert]

A number of issues have been cropping up that seem to be related to changes in library naming and structure. Much of this may be related to the Python 2-->3 transition, and the fact that GSFLOW-GRASS was built for Python 2.7. (This is in addition to any changes from newer versions of GRASS GIS.) From my initial pass through the code base, this will take some significant effort in building and restructuring. I am trying to decide whether continued support here is warranted, or is likely to become a major and unproductive time-suck as GSFLOW, GRASS, and Python continue to update and I am just one person who does not plan to use GSFLOW in the near future for his work. Thoughts and voluntary co-development appreciated!

[jvollhueter]

Hello, I am currently writing my Master Thesis at the Technische Universität Dresden and I am using GSFLOW-GRASS for the pre-processing of my models. Among other things, I have created a very simple synthetic model, which could help people who are starting to deal with GSLFOW-GRASS and GSFLOW in general to understand the process of the software and I am currently writing a visualization tool with Python 3. I am generally very interested in getting further into coding, but have also worked with Python before. If you are interested in me contributing to the further development of GSFLOW-GRASS, feel free to contact me. I would have time for this starting in April.

Best Regards

Jonas

[awickert]

Hello @jvollhueter. My apologies for not checking here -- if you are interested in further developing GSFLOW-GRASS, I would very much encourage you to take our code and run with it. Please feel free to contact me here and/or to write me an email.