> Jeremy> Various lyx code has "python" hardcoded. It may be good to > Jeremy> take advantage of the PYTHON setting. > > Jeremy> Some systems do not have a "python" in the path, but may have > Jeremy> python2.4 for example. > > That is very weird, isn't it? Which system?
DragonFly and NetBSD systems. PkgLinux. Maybe BlueWall Linux, Nethence Linux and VoltaLinux. Yes, a "python" symlink or wrapper can be installed. But for consistency using the known version like "python2.4" seems better. Several operating systems allow different versions of python to be installed -- but what if they change? Now I see this argument can go both ways :) Maybe this can be some ./configure option for this. > Jeremy> Here is a list of files below. > > Jeremy> Some of these python scripts are fine at the top sh-bang #! > Jeremy> line, but later inside of same file that may call "python" > Jeremy> again. > > Which ones? lib/doc/depend.py lib/configure.py Also lib/scripts/listerrors and development/tools/generate_symbols_list.py does not use "env" technique. > Jeremy> src/buffer.C src/lyxtextclass.C > > In the source, we can use something like what is done in trunk (use > os::python instead of "python"), which would allow to change the > command used. I would like to be sure first that the bug is not on the > system side :) - Jeremy C. Reed
