On 2014-03-15, Benjamin Piwowarski wrote: > This is related to bug http://www.lyx.org/trac/ticket/8950
> The problem is the following. Currently, to find python2, LyX: > - checks the python command is a valid python 2 executable > - if so, it just stores that the python command is “python” (otherwise, > it searches and uses an absolute path - leading to no bug) > - when reading lyxrc, or changing preferences, the PATH might be > changed. If (and it happens) the first “python” in the PATH is python > 3, then LyX breaks completely (on OS X, no menu is displayed, nothing > happens). I propose to make all LyX's Python scripts compatible with both, Python 2 and 3. For complex scripts, this could mean a version-test at runtime in a wrapper that subsequently imports the correct module or sets sys.path appropriately... Günter
