Comment 6 for bug 482993

This is all very strange. 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. 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 .so files are linked against. BTW, I also tries specifying a "DYLD_FALLBACK_FRAMEWORK_PATH" but that didn't seem to help.

I was considering building lxml against the Snow Leopard's xml2, xslt and exslt libraries but this is apparently not recommended by the lxml people since the versions distributed with OS X are out of date and cause problems -- this is true for older OS X versions, I haven't checked for sure it is true for the versions distributed with Snow Leopard.

After more investigation, I think the right way to do this might be to build versions of the lxml and numpy extensions with the "--static-deps" option to the "setup.py" build script. This will download and build the most recent xml libraries as part of the build process and then the extension should not depend on anything. Haven't got it building completely yet, but this is what I will test next, maybe tomorrow night.

FWIW, I can't really understand why the prebuilt extensions we have work with Apple's python 2.6 but not the Macports version, but thanks for your testing ~suv and Alexey, this is another avenue to pursue I guess.