Re: Call for changes in the Python library

Hi Laurent,

On Fri, Sep 25, 2020 at 2:53 PM Laurent C. <[email protected]> wrote:

>
> From my experience, the temporal framework is rather quirky, and might be
> in need of refactoring to fix some of those quirkiness (see for example
> https://github.com/OSGeo/grass/issues/629).
> Most of it might be done without breaking the API, but the new major
> version could be an opportunity to break things for the better.
>

This sounds great. There are a lot of tests in place, so that's a good
starting point. I would be happy to discuss the details if you can work on
the changes. Having a bigger flexibility with mapsets makes sense to me.

Best,
Vaclav

PS: Check a recent PR on GitHub for init/connect.


> Cheers,
> Laurent
>
>
> Le jeu. 24 sept. 2020 à 21:29, Vaclav Petras <[email protected]> a
> écrit :
>
>> Dear all,
>>
>> Now would be a great time to do any large or small changes in the Python
>> library. Let's discuss these. For example, there was a talk about more
>> clear splitting of the ctypes dependent and independent code in
>> grass.pygrass, about moving the library to a different place, there is the
>> new grass.grassdb subpackage, PEP8/Black/Flake8, ... Is there anything
>> *you* see as a priority for 8.0? Is there anything you can do before 8.0?
>> Let's coordinate here.
>>
>> Best,
>> Vaclav
>> _______________________________________________
>> grass-dev mailing list
>> [email protected]
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>

_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev