Re: [GRASS-dev] grass-session integration into core

[Stefan Blumentrath]

Hi,

Appreciate the discussion!

I also agree with Vasek here.

GRASS session is very useful, esp. in standalone python scripts or when using 
GRASS in Jupyter notebooks, or maybe in QGIS Processing for that matter
However, since grass-sessions is an external Python module it has had issues 
due to version changes before.

So, a big +1 from my side to include it in core, knowing that my ability to 
contribute here with coding is very limited...

Being able to just do

import grass

would be nice indeed, but I am not sure if it is feasible to throw an 
informative error message if users try to use GRASS functions without a running 
session...

That said, what would the gain of a pip package be? If you install GRASS you 
would have the functionality. If you did not install GRASS you could not use a 
pip package with grass-session like functionality anyway, no?

Cheers
Stefan

From: grass-dev  On Behalf Of Markus Neteler
Sent: onsdag 9. juni 2021 08:55
To: GRASS developers list 
Subject: [GRASS-dev] grass-session integration into core

Hi devs,
Vaclav Petras mailto:notificati...@github.com>> 
schrieb am Mi., 9. Juni 2021, 05:22:

...anyway, I think the ultimate fix is to build usable images from GRASS source 
code without a 3rd party library which is not an official dependency. Either 
GRASS needs grass-session to work and then it should be part of the source code 
or GRASS should be fixed to work without it.

-
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on 
GitHub,

Following this comment I'd like to open the discussion: also in my view we need 
to make grass-session part of core. And that in a way that it can be split out 
easily as a pip package or whatever appropriate.

Opinions are welcome!

Best
Markus

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8: create new release branch

[Maris Nartiss]

Hello Veronica,
thanks for pushing this forward.

Looking from a "it is ready when it is ready" perspective – what we
are missing from functionality to call 8.0 ready? (I mean only things
that are expected to be ready in less than a month)

From my side:
Band references and integration with signature files are ready to be
merged (please review!), missing functionality can wait for 8.2.
https://github.com/OSGeo/grass/pull/1272
https://github.com/OSGeo/grass/pull/1501

I'll try to work on r.in.pdal this Friday (I need to do some LiDAR
work myself). It is almost merge ready (as long as we add extra
functionality in 8.2)
https://github.com/OSGeo/grass/pull/1200

Then from my side I'd call 8.0 ready.
Māris.



2021-06-08 17:09 GMT+03:00, Veronica Andreo :
> Hello devs,
>
> As you all know, grass birthday is approaching... July 29th is just around
> the corner. I'd love to celebrate GRASS' bday with a new release, with a
> big release ;)
> Do you think that is doable? How much is missing for GRASS 8 release?
>
> The next important date is FOSS4G 2021 on September 27th - October 2nd,
> where we have proposed GRASS 8 talks and workshops. If we can't make it for
> GRASS GIS' birthday, do you think it's feasible to release before FOSS4G,
> say August for example?
>
> I think it's really important to agree on a date so we can all manage our
> reduced time and focus our efforts towards that aim.
> What do you say?
>
> Best,
> Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] grass-session integration into core

[Markus Neteler]

Hi devs,

Vaclav Petras  schrieb am Mi., 9. Juni 2021,
05:22:

> ...anyway, I think the ultimate fix is to build usable images from GRASS
> source code without a 3rd party library which is not an official
> dependency. Either GRASS needs grass-session to work and then it should be
> part of the source code or GRASS should be fixed to work without it.
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> ,
>

Following this comment I'd like to open the discussion: also in my view we
need to make grass-session part of core. And that in a way that it can be
split out easily as a pip package or whatever appropriate.

Opinions are welcome!

Best
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev