I just tried to convert my SVGs via LyX again and the problem is still there, even with removing pythonw.exe
In this bug and in: https://answers.launchpad.net/inkscape/+question/89609 I claimed that renaming the files would fix the problem, but that was a mistake. I just thought it worked because my LyX used cached versions of the converted EPS-files (converted correctly from my SVGs by inkscape 0.46).
Therefore, this bug has a wrong title and description. Maybe it should be renamed:
Inclusion of python.exe in 0.47pre4 causes 3rd party commandline usage problems
The actual problem is the following:
Inkscape seems to look for it's own python.exe and uses that one if found. When inkscape uses it's own python my LyX generates empty documents (documents without images). I am not sure whether the problem results from LyX using the "wrong" Inkscape python, or whether the problem is caused by Inkscape using it'using it's own python. I just see the commandline popping up. In the title of the window i see which python is used, but not who invoked it.
Workaround:
You can "fix" this problem by deleting python.exe from the inkscape/python folder. Then inkscape (via LyX?) uses LyX's python (C:\Lyx\python\python.exe in my case). This produces valid documents containing the converted EPS-images. But i still see commandline popups, which shouldn't be the case.
Problem Investigation:
When using inkscape 0.46 (leaving it's own python untouched) I have no problems and NO commandline popup. Maybe the Inkscape internal python invocation is simply missing the "do not show commandline"-flag?
I just tried to convert my SVGs via LyX again and the problem is still there, even with removing pythonw.exe
In this bug and in: https:/ /answers. launchpad. net/inkscape/ +question/ 89609 I claimed that renaming the files would fix the problem, but that was a mistake. I just thought it worked because my LyX used cached versions of the converted EPS-files (converted correctly from my SVGs by inkscape 0.46).
Therefore, this bug has a wrong title and description. Maybe it should be renamed:
Inclusion of python.exe in 0.47pre4 causes 3rd party commandline usage problems
The actual problem is the following:
Inkscape seems to look for it's own python.exe and uses that one if found. When inkscape uses it's own python my LyX generates empty documents (documents without images). I am not sure whether the problem results from LyX using the "wrong" Inkscape python, or whether the problem is caused by Inkscape using it'using it's own python. I just see the commandline popping up. In the title of the window i see which python is used, but not who invoked it.
Workaround: python\ python. exe in my case). This produces valid documents containing the converted EPS-images. But i still see commandline popups, which shouldn't be the case.
You can "fix" this problem by deleting python.exe from the inkscape/python folder. Then inkscape (via LyX?) uses LyX's python (C:\Lyx\
Problem Investigation:
When using inkscape 0.46 (leaving it's own python untouched) I have no problems and NO commandline popup. Maybe the Inkscape internal python invocation is simply missing the "do not show commandline"-flag?