[GRASS-dev] [release planning] 7.6.0
Stefan.Blumentrath at nina.no
Sun Aug 26 23:05:21 PDT 2018
From the final report it seems that there are still some open issues, esp. with pygrass and the temporal library (because of ctypes):
From: grass-dev <grass-dev-bounces at lists.osgeo.org> On Behalf Of Moritz Lennert
Sent: mandag 27. august 2018 07:59
To: grass-dev at lists.osgeo.org; Markus Neteler <neteler at osgeo.org>; GRASS developers list <grass-dev at lists.osgeo.org>
Subject: Re: [GRASS-dev] [release planning] 7.6.0
Am 27. August 2018 07:52:22 MESZ schrieb Markus Neteler <neteler at osgeo.org>:
>On Mon, Aug 27, 2018 at 3:35 AM Anna Petrášová <kratochanna at gmail.com>
>> On Sun, Aug 26, 2018 at 12:35 PM Michael Barton
><Michael.Barton at asu.edu> wrote:
>>> Blockers #3617 and #3621 apply to 7.6 as well as 7.4. Broken in all
>versions 7.4.1 on up. No way to
>>> get a map out of GRASS on the Mac.
>> Some of these may be fixed in the patch provided by Sanjeet as part
>of GSoC when she was
>> working on wxPython4 compatibility. So I would first put her changes
>Can you please point us to the latest patch?
>> (once we create the new branch) and then backport selected fixes.
>I was thinking about it again: we are yet one of the few packages
>requiring Python2. What if some of us try the Python3 patch and give
>feedback (of course an ideal thing for a git branch...)?
>And then, if nothing dramatic goes wrong, we merge it prior to creating
>Reflecting about our common release frequency I fear that we end up
>with 7.8 in the (far) future to make GRASS GIS ready for Python3.
>So: I volunteer to patch locally and test etc. the new Python3 support.
I think Python 3 support should be a must nowadays.
I didn't follow Sanjeet's GSoC work very closely. How far are we in theory with Python 3 support with her patches ?
I also volunteer to test.
grass-dev mailing list
grass-dev at lists.osgeo.org
More information about the grass-dev