Laurent Courty

@zarch I do not know much of the internals of the temporal framework, but it seems that it sets several global variables at invocation: https://github.com/OSGeo/grass/blob/5ae98b8f29cf011442f8a7f1cee9de0f763fda0b/lib/python/temporal/core.py#L130-L134 Maybe some of them are...

@wenzeslaus I understand that the GRASS scripting library runs each command in a subprocess. Calling modules is not very pythonic (expecting files instead of objects, etc.), and if the code...

@wenzeslaus I wonder if encapsulating those functions and variables in a class could be possible, because it might help solve the issue. It would be a major refactor because those...

I'll link here the [discussion about the issue in the mailing list, back in 2016](https://discourse.osgeo.org/t/grass-dev-working-with-tgis-without-starting-grass-explicitly/82077/6).

I just encountered the exact same issue and I'd like to know if there is something I do wrong or a workaround. I use pyperf 2.9.0

It seems to be a QGIS issue (how the GRASS tool is represented in QGIS), rather than a GRASS issue. The related [parser option](https://github.com/OSGeo/grass/blob/193579448e84c26e98f04e97918b6c61d5a2adff/temporal/t.register/t.register.py#L75C1-L84C7) in `t.register` clearly states that the...

Thank you for looking at this @jsignell ! If this helps, my workaround for now is to write directly using zarr (only one value in the appended time coordinate): ```python...

I wonder if #9154 and #3942 are related?

You need to first import grass_session, then you can import grass.script