Anna Petrasova

> Is there a way to do the math once manually or symbolically to have the truth? It's too complicated for that unfortunately.

> It's not a huge issue, but it would nice to 1) be consistent, which it is not currently, and 2) clearly signal to users what a GRASS Project is....

See #3020 for tracking modules that need JSON/YAML output.

We have been trying to use this, but it hasn't become part of documentation yet: ``` def main(): options, flags = gs.parser() ... if __name__ == "__main__": main() ```

@cwhite911 see the discussion we had in https://github.com/OSGeo/grass/pull/3480#discussion_r1519351514, we basically decided not to use the -s flag, so this PR needs to be updated...

@isaacnewtonfx Does this happen in any mapset? Could you attach the content of the WIND file? When you run g.gisenv in the terminal, the WIND file will be in GISDBASE/LOCATION_NAME/MAPSET...

> 1. This is a drastic enough change for how users interact with GRASS, even if backward compatibility, that it should be done only with the launch of a new...

> @cmbarton I feel the same way. Even though it'll be only the label that changes until phase 4, it can be confusing to new and existing users as well...

@HuidaeCho, would you have any suggestion for a different tool that could be easier to implement parallelization for? I don't think there are many low hanging fruits, but maybe v.surf.idw?

> > > > Also, what are the atexit, gs and sys empty files? > > > > > > > > > @veroandreo where do you see these empty...