On 11/21/2014 09:23 AM, Kornel Benko wrote:
Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck <rgh...@lyx.org>
On 11/21/2014 08:25 AM, Alex Vergara Gil wrote:
Ok, let me be splicit. I use extensively Spyder with python 3 for my
work, I use also LyX to write my articles. When I installed LyX (on
windows) it uses its own bundled python2 and it works fine. The
problem arises when I want to import my python graphics into LyX,
which should be interpreted with python3, I try putting python3 into
LyX and then LyX stops working at all!! it doesn't reconfigure
anymore, and when I try to start it, it crashes with a big failure. So
I am forced to produce python2 only graphics.
Yes, that is what I would expect.
to reference this is the article in which I show how to add python
graphics within LyX>
http://article.gmane.org/gmane.editors.lyx.general/82745/match=python+graphics
It might be possible to specify the full path to the python version you
want to use in
the relevant converter definition. But I am not sure.
Richard
We use hard-coded strings for python calls.
Examples:
./src/support/ForkedCalls.cpp:308
./src/support/Systemcall.cpp:170
./src/support/filetools.cpp:410
./src/graphics/GraphicsConverter.cpp:276
so that full path is not helpfull.
It looks as if this is searching for "python -tt" at the beginning of
the command,
and then replacing that with an explicit call to python2. So if one gave
the full
path in a converter to python3, then it should work. Alternatively, one
could
create a symbolic link to python3, with some other name, and call that.
On unix I can make a symbolic link e.g.
# ln -s /usr/bin/python3 $HOME/bin/python
and lyx is still working. ($HOME/bin is at the beginning of my path)
Confirmed (though on Linux, too).
Richard
