rgheck schrieb:
ImportError: No module named genericpath
Error: Conversion script failed
This was a bug in the Windows installer for RC5 that I fixed in LyXWinInstaller version 4.12 a day
later.
I just released installer version 4.13 that comes with the final LyX 1.6.0. I recommend to uninsta
Paul A. Rubin wrote:
rgheck wrote:
I think Uwe made some kind of change to python in the Windows
installer, so maybe that is the issue here. But the real question is:
Does this problem persist in 1.6.0?
Nope. Just installed and tested 1.6.0, and it opened my 1.5.x test
doc fine.
OK,
rgheck wrote:
I think Uwe made some kind of change to python in the Windows installer,
so maybe that is the issue here. But the real question is: Does this
problem persist in 1.6.0?
Nope. Just installed and tested 1.6.0, and it opened my 1.5.x test doc
fine.
/Paul
Paul A. Rubin wrote:
Richard Heck wrote:
Paul A. Rubin wrote:
I just discovered that LyX 1.6.0rc5 will not import *any* of my
older (1.5.x) LyX documents (lyx2lyx always fails). This is on Win
XP. Is this something that's known (and hopefully fixed)?
I think we had another report like this
Richard Heck wrote:
Paul A. Rubin wrote:
I just discovered that LyX 1.6.0rc5 will not import *any* of my older
(1.5.x) LyX documents (lyx2lyx always fails). This is on Win XP. Is
this something that's known (and hopefully fixed)?
I think we had another report like this, and I think it is fi
Paul A. Rubin wrote:
I just discovered that LyX 1.6.0rc5 will not import *any* of my older
(1.5.x) LyX documents (lyx2lyx always fails). This is on Win XP. Is
this something that's known (and hopefully fixed)?
I think we had another report like this, and I think it is fixed. Can
you try run
I just discovered that LyX 1.6.0rc5 will not import *any* of my older
(1.5.x) LyX documents (lyx2lyx always fails). This is on Win XP. Is
this something that's known (and hopefully fixed)?
/Paul
