Am 25.03.2014 um 03:26 schrieb Uwe Stöhr <uwesto...@web.de>:

> Am 24.03.2014 08:13, schrieb Stephan Witt:
> 
>>> But this is then not possible. For example the user once used LyX 2.0.3 and 
>>> Python was on
>>> E:\Programs\Python
>>> He did not use LyX for a year or so and now installs LyX 2.1.0. Since LyX 
>>> 2.0.6 the LyX Win installer comes ALWAYS with its own stripped down Python 
>>> so that the preferences created by the installer has the right part to the 
>>> stripped down Python. If you now copy the preferences of the former LyX 
>>> 2.0.3 to LyX 2.1.0 you cannot reconfigure LyX anymore if Python is no 
>>> longer under
>>> E:\Programs\Python
>>> (maybe it is now on another network drive or whatever)
>> 
>> Python detection is not the task of the installer.
> 
> Stephan, please re-read my post. I clearly explained what the problem is and 
> we have the clean solution for Python first since LyX 2.0.5. All releases 
> before can show the problem I described.

I did it and I cannot see what is wrong with "Python detection is not the task 
of the installer."

Because LyX is unusable without it LyX should use the correct python detection 
itself.
On Unix this was simply using the PATH. Since python 3 is more common the 
lookup is
a little bit more complicated. If using PATH isn't the right thing on Windows 
then it
has to be done in the Windows way from inside the LyX binary itself. 
Unfortunately
it's not possible to use python for this task… If providing a bundled python 
installation
is an acceptable alternative solution then do it this way.

Stephan

Reply via email to