On Wednesday, 26 June 2019 11.40.07 WEST Stephan Witt wrote: > Hi José, > > I’m not surprised at these explanation. > > The real world scenario would be to disable python 3.4 on my system > and test it with 2.7.15 - this works for me.
That is what I am proposing. :-) > But - if it’s clear LyX doesn’t work with python 3.4 why is it tried and > used? Or is it this what you propose? Change the tested minimal python > version from 3.3.0 to 3.5.0? Then I’ll cannot agree more. That is also my point. At some point during the process we settled on python 3.3 because it supports the u"" notation. In python 2 those mean unicode strings (strings with an encoding as to differentiate them from the usual "" strings that are basically an array of bytes). In python 3 u"" is a no-op because all the strings have an encoding associated. Until python 3.3 the u"" notation gave an error. Again this notation was introduced to allow an easy migration to python 3 by using a common code base. It is the same reasoning as in the previous case. So I am really proposing is to accept as the minimum version for python 3 the 3.5 release. There are three places to change: * os::python23 function in support; * autotools support; * cmake; We should be simply a matter of replacing 3.3 by 3.5. > Best regards, > Stephan -- José Abílio
