So I uninstalled Inkscape as well, removed my own definition of PYTHONPATH, and did a clean install of both Python and Inkscape. I used to have some pre-existing Python 2.7.x, but managed to uninstall that while I was hunting the "fantastic syndrome".
Next, I figured out that the other way out would be to avoid installing Python within the Inkscape installer, and rely on a system-wide Python. I don't recall the precise error message, but it just didn't work out. That did not succeed to install pip (which IMO is a requirement before "pip install lxml"). So I set the PYTHONPATH, launched a CMD with admin privileges, CD'ed into \Program Files\Inkscape, downloaded a copy of get-pip.py and ran that within the Inkscape Python environment.
I quickly realized that in my case, the "Inkscape's own" Python was possibly missing the lxml library. At the same time, it disrupted my system-wide python instance - guess why :-) In my case, this didn't make a difference to Inkscape, the problem with missing lxml was still there all the same. To solve the "fantastic" syndrome, some recommend to set the PYTHONPATH environment variable (system-wide if need be) to point to the Inkscape's own Python library folder. There's even a python.exe.įor comparison: the standard system-wide Python lives in C:\Python27\ by default. Instead, it lives in C:\Program Files\Inkscape.
The EXE installer definitely does contain a check mark in that vein, not sure about the MSI installer variant (I seem to recall that the set of selectable options is not as rich in the MSI installer variant).Īnd here comes the catch: this Python runtime, as installed by Inkscape, is not installed system-wide. Regardless of whether you have some Python on your PC already or not, the Inkscape installer offers to install Python along with Inkscape (an option in the installer). Python is a popular interpreted language and it can so happen that you have a pre-existing system-wide install of Python (some version) on your PC, at the time you install Inkscape. This means that a Python runtime engine is needed for those functions of Inkscape to work. Note that the "Technical details" of the error message seem to be different with different people = they are likely a host of various underlying problems, resulting from different misconfigurations surfacing in different people's Windows system images, or possibly different glitches occuring in the Inkscape installer package for Windows (various historical versions).įirst of all: note that some "peripheral" stuff in Inkscape is implemented as Python scripts or modules - such as, file imports and exports (some formats at least, mine was the DXF) and maybe the built-in help. I've just faced "this" bug in Windows 7 64b and InkScape 0.92.2 and I'd like to give a little talkative answer, to shed some light on the background of this "fantastic" phenomenon.
0 kommentar(er)
