How to test local cli.py changes without full compilation?

[tangelll]

Hi everyone,

I'm working on the --link-raster task and I've modified the cli.py file. I'm trying to test it locally on my Mac, but I'm stuck with a path issue:

If I run GRASS normally, it uses the system installation and doesn't see my new code.

If I use PYTHONPATH to point to my local folder, I get this error:
FileNotFoundError: /usr/local/grass85/etc/@GISBASE_INSTALL_PATH@/etc/clean_temp

I understand this is because my local source is not compiled and has these "placeholder" paths.

Since I'm only changing the Python code in cli.py, is there a simple way to test this without compiling the whole GRASS project from source? Or should I just open a Draft PR and use the CI/CD tests to see if it works?

Thanks!

[echoix]

Since it is Python, thus not compiled, you could directly edit the installed file, or copy your edited file there (if there's no placeholders that were replaced at compile-time/install-time). Remember what you did and know how to clean/reinstall it when it goes wrong.

I edit the installed files of an osgeo4w grass install on windows. On macOS, these files exist somewhere (but I cannot help you locate them).

[tangelll]

Hi @echoix , I’ve successfully implemented and locally tested the --link-raster parameter in cli.py. I’m currently finalizing the tests for the other parameters. Could you please assign this issue to me? I’ll submit a Draft PR shortly. Thanks.

[echoix]

Could you please assign this issue to me? I’ll submit a Draft PR shortly. Thanks.

If you wish so, we don't use that as rigorously