PYTHONHOME conflict in using gdb to debug GRASS GIS C modules on Windows 11 about grass HOT 1 CLOSED

As per comments received in response to my question here -

https://stackoverflow.com/questions/77972748/how-do-i-get-an-application-using-python-to-ignore-pythonhome-and-or-pythonpath

I am able to resolve this by creating a .gdbearlyinit file located at C:\Users\User\.gdbearlyinit, containing the line

set python ignore-environment on

gdb can now be invoked either from the grass command line (in a cmd.com windows terminal; I have not tried it inside the GRASS GUI builtin terminal) or as the debugger of choice within VSCode.

This may be a useful addition to https://trac.osgeo.org/grass/wiki/CompileOnWindows if someone with write access to that page could make the edit.

from grass.