On Thu, Nov 20, 2014 at 11:36 AM, Richard Heck <rgh...@lyx.org> wrote:
> On 11/20/2014 09:55 AM, stefano franchi wrote: > > On Thu, Nov 20, 2014 at 2:09 AM, Scott Kostyshak <skost...@lyx.org> wrote: > >> I cleaned RELEASE-NOTES for the master branch. This note is still >> relevant right? >> >> - LyX needs to be run under Python 2 and will not work properly on systems >> where Python 3 is the default binary. See bug #7030 to know how to fix >> this properly, since simple sheebang conversion in *.py files will not >> be enough. >> >> >> I've seen some references here and there (e.g. Benjamin's work on >> features/python3), but Python 3 incompatibility is still in master >> right? >> > > Actually, I thought this problem was solved a couple of years or so ago > (about Lyx? 2.0.2) > I used to have problems on my ArchLinux box (with python 3 as a default) > but that is no longer > the case. > > > There are two different issues here: (i) Will LyX work when Python 3 is > the default? (ii) Will > LyX work with Python 3? The answer to the former is "Yes", as long as > Python 2 is available: > We now look for it explicitly. The answer to the latter, I believe, is > "No": The LyX scripts will > not run under Python 3, though some work has been done on that, as Scott > mentioned. > > That's my experience on Linux. However, Alex seemed to suggest (i) is not completely true on Windows. If I understood his point correctly, LyX will work when python 3 is the default by installing its own python2 interpreter, which proceeds to break things (which things, I am not sure. Alex did not say). So perhaps there are three cases: (i) Will LyX work when Python 3 is the default, but Python 2 is available? (ii) Will LyX work with Python 3? (iii) Will LyX work when Python 3 is the default and LyX install its own version of Python? And he answers are yes, no, kind of? S. -- __________________________________________________ Stefano Franchi stefano.fran...@gmail.com <stef...@tamu.edu> http://stefano.cleinias.org
