Anna wrote: > Unable to fetch interface description for command > 'd.rast3d'. > Details: [Errno 2] No such file or directory > > So it cannot find the command. I couldn't find any solution, > maybe someone else knows what's going on? > I found related ticket here [1]. > [1] http://trac.osgeo.org/grass/ticket/1515
see also https://trac.osgeo.org/grass/ticket/1692 and friends. d.rast3d.py fails because it is not in the PATH. on the first pass of a grass script it gets very quickly to the g.parser module, which then *re-runs* the same script but with the ARGS_PARSED environment variable set so that on the second pass it runs the script body and not just g.parser. If the module is not in the PATH, then when g.region tries to run it it can't find it by name. I guess the full path in $0 either isn't there or gets stripped off? The common module scripts are all installed in the PATH, so it shouldn't be a problem to find them (except on wingrass it is, see #1692), for the few GUI-helper scripts and "etc" helper scripts like i.oif has it is worse since the script needs to do like PATH="$PATH:$GISBASE/etc/i.oif"; export PATH before running g.parser if it wants the helper scripts to be found. (actually that's a fake example as i.oif's helper scripts don't use g.parser) For the python GUI helper scripts it is even worse still because AFAIU include/Make/Python.make is not doing all the things in GRASS 6 that Script.make (exclusively for shell scripts) does. For WinGrass it's even worse again as we need .bat wrapper scripts for the shell scripts in the %PATH% which point to the right place. For python text scripts on WinGrass hopefully the minor version of the python it happens to find at run time doesn't matter too much as long as it's 2.4+. Q: Is anyone using python addons scripts with GRASS 6.4.2? does it work fine? not at all? ?? needing to be at in the main scripts PATH It's certainly possible to fix all this, but best worked on when your brain sugar is at high levels. :) Hamish _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
