BTW, I also tries specifying a 'DYLD_FALLBACK_ FRAMEWORK_ PATH' but that didn't seem to help. I still can't get this to work and have come to the conclusion that maybe Inkscape launches a python executable and that has it's own executable_path and so does not look for the libraries that the python lxml.

I have spent a bunch of time this weekend trying to get the extensions to work under Snow Leopard, mainly by taking versions installed by macports and rewriting the paths to point to versions of libraries in the app bundle. In particular, the workaround in bug #345176 does not work. I've seen a few other bug reports for extensions, but none of them seems to describe the exact problem we encountered. I suspect that the 2.6 binary is running with the x86_64 architecture, which isn't present in the etree.so library.Īs a workaround, I symlinked /usr/bin/python to point to python 2.5 (which is a 'Mach-O fat file with 2 architectures'), and that makes the extensions work again. The python 2.6 binary is a 'Mach-O fat file with 3 architectures', while the etree.so shipped with lxml is a 'Mach-O fat file with 2 architectures'. I investigated a little bit, and it seems that lxml doesn't work with the python 2.6 shipped with Snow Leopard. Printing out the real exception, this was due to dlopen not working. org/pypi/ lxml/, or install it through your package manager by a command like: sudo apt-get install python-lxml Please download and install the latest version from cheeseshop. The fantastic lxml wrapper for libxml2 is required by inkex.py and therefore this extension.

After installing Inkscape 0.47 pre4, we found that extensions don't work and give the infamous lxml error message:

Update inkscape mac