>  I never liked that behavior but the consensus was to act this way. The
>> problem is also here the time. E.g. a users worked the last time with
>> LyX 2.0.2 then he did not use it for a year and uninstalled it. Now he
>> installs LyX 2.0.7 but will get the preferences from hos old 2.0.3. ->
>> error prone because e.g. Python might once have been on a network drive
>> which does no longer exists.
>>
>
> If python moves without notification you have a problem even if LyX has
> not been uninstalled...
>
> But again: why on earth would the python path be stored in the preferences
> file? This file should contain only the changes done explicitly by the
> user. If it contains something else, we have a bug.
>

What exactly do you propose then ? Do you propose to have LyX determine the
Python location on run-time ? Would this mean to search the whole harddrive
for a python.exe ? Would you want to store the python path in the Windows
registry instead ? Would you want to hardcode this into configure.py to
look for "../Python/python.exe" explicitly ?



>
> From what you say, I suspect that you installer modifies the preferences
> file. Is this the case? It would be terribly wrong.
>

Isn't that where we have lyxrc.dist for  ? So, it might not be as terribly
wrong in general (I'm not talking about the path specifically).


>
> JMarc
>

Vincent

Reply via email to