Assuming it was did with the help of a tool the same way as the other PRs, it looks good to me. If there are some parts you'd want me to look more attentively in an IDE, tell me here before we merge

I basically listed out all function calls and added them. I had tried using GPT for this, but it misclassifies some functions like it did in a similar PR previously. Subsequently I ran isort on them

If you use vscode, why not activate pylance/pyright? It'll discover the methods and modules and you won't have to fear hallucinations. You'll have the autocomplete suggestions feeded through the LSP protocol.

I'll try to open it myself next time I'm on a computer with time for this.

If you use vscode, why not activate pylance/pyright? It'll discover the methods and modules and you won't have to fear hallucinations. You'll have the autocomplete suggestions feeded through the LSP protocol.

Got it! I'll try it out next time I have a similar PR

@echoix I looked at it in iDE, and it matches the functions on the files

I don't know how well we could check it, but is there a way to do a little double check on the gui tools that use this module? It's less used than grass.script, so it might be possible to search for all references.

Recently there was an overlook that ended up having grass.script.named_colors not being exposed anymore, and a gui component wasn't working anymore. Since the gui code is poorly tested (I'm being generous here), we didn't catch it until a bug was filed. See #4825 and the issue it fixed.