On Wednesday, 29 March 2017 15.25.12 WEST Kornel Benko wrote: > > > There is one task remaining. Creation of lyxrc.defaults uses string > > > 'python' as executable even if lyx is configured for use with python3. > > > I agree that this could change.
Actually here I meant to say not just that it could but the it *should* change. > > > I had to edit this file to get the desired python3 to run the converts. > > > (Example: \converter fig pstex "python -tt > > > $$s/scripts/fig2pstex.py $$i $$o" "") > > > Honestly here I suggest us to change this automatically for users. > > If the first command is python we should change it to the python version > > configured. If the user wants to use a different python version the user > > is > > free to use say "python2 -tt ..." > > > > For example in my system where python is python2 I have: > > $ ll /usr/bin/python > > lrwxrwxrwx. 1 root root 7 Jan 12 18:00 /usr/bin/python -> python2 > > $ ll /usr/bin/python2 > > lrwxrwxrwx. 1 root root 9 Jan 12 18:00 /usr/bin/python2 -> python2.7 > > > > And that has been like this for ages. > > yes, it is the same here. But I don't want to change the symbolic link > because it may influence some other programs. > Instead I'd prefer to have an option to tell lyx to use python3 for handling > of lyx-local python scripts. In case it was not clear I mean that we should do it inside lyx because the python2 and python3 names are *always* available. So in every place where we have the python name as the first command we should change it to python2 or python3, like if in a sense python meant $$python that we replace by the appropriate python name. This way it will work for everyone and someone that needs can pin the python version by directly placing the major version in front of the python name. I hope that this is clear now. :-) Regards, -- José Abílio
