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 <grass-dev-boun...@lists.osgeo.org> On Behalf Of Markus Neteler Sent: onsdag 9. juni 2021 08:55 To: GRASS developers list <grass-dev@lists.osgeo.org> Subject: [GRASS-dev] grass-session integration into core Hi devs, Vaclav Petras <notificati...@github.com<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<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fpull%2F1624%23issuecomment-857341278&data=04%7C01%7C%7C0986cc6aea0f4415406208d92b138ceb%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637588185234423158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X8lKLIFGs0xQC%2FhcmXPvFGkKzDyaf%2FNkAAA7yJKgzbg%3D&reserved=0>, 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
