Am Samstag, 19. August 2006 15:10 schrieb Jeremy C. Reed: > Yes, a "python" symlink or wrapper can be installed. But for consistency > using the known version like "python2.4" seems better.
No. That implies that LyX can only use version 2.4, and that is wrong. Installing "python2.4" is good, because you can then call python 2.4 explicitly if you need exactly that version. Not installing "python" is bad, because in my experience many python programs are not as strict and work with any version 2.x or even 1.5. > Several operating systems allow different versions of python to be > installed -- but what if they change? LyX can work with many python versions. The minimum for 1.4 is 1.5.3, and the minimum for 1.5 is 2.3. All later versions work AFAIK. > 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. I guess it should be easy to get the name of the running python interpreter and use that instead. > > 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 :) IMO it is on the system side. An OS should provide a generic "python" executable for programs that are tolerant WRT python version. Georg
