Has anyone gotten scripts to work under Snow Leopard. I have looked through the forum and tried a bunch of the suggestions, but am still getting a lxml missing error. I have checked and the system python26 has lxml, so does the system python25. Any ideas how to fix this? Or anyone else having this issue?

As an update to this it seems to be specific to etree from lxml...


Any ideas?

Unfortunately, this is a known issue with current prerelase packages for Leopard and Snow Leopard. See this posting on the inkscape-user mailing list. I do not know of any available "quick fix" yet.

EFaden wrote:As an update to this it seems to be specific to etree from lxml...

Code: Select all

python -c "from lxml import etree"Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/lxml-2.2.2-py2.6-macosx-10.5-i386.egg/lxml/etree.so, 2): no suitable image found.  Did find:
        /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/lxml-2.2.2-py2.6-macosx-10.5-i386.egg/lxml/etree.so: mach-o, but wrong architecture

Questions:

• you did rebuild your complete MacPorts tree after upgrading to Snow Leopard as recommended? Because 'mach-o, but wrong architecture' should not happen (besides the Inkscape extensions issue) if you correctly installed the python modules via MacPorts.
• did you check with 'which python' if you were using the one from MacPorts and not the system-supplied python version (which might be 64bit whereas the MacPorts modules are i386 or vice versa) when testing (as quoted) the lxml module?

[Edit] after re-reading your post I realize my inital assumption was wrong: the path to '/opt/local…' didn't come from your local python installation but from the site-packages inside the Inkscape bundle? [/Edit]

Another hint:

• The default prerelease packages have all necessary python modules included - if you want to use those installed with Macports you would need to change the shell laucher script inside the Inkscape package (setting $PYTHONPATH to the site-packages in '/opt/local' or the python framework installed by Macports). But as the modules installed there don't seem to work either that doesn't help you right now.
• python extension related bugs: #421305 (SL), #424138 (MacPorts), #345176(Leopard)

Got it. Somehow the ones included in the .app weren't working. I commented out the PYTHONPATH line in the startup script to get it to use my system one. Who knows what was wrong with the build, but I just deleted the lxml port and then reinstalled it and the system one started to work. All is well now....

Thank you for the feedback!

If you don't mind I'll add a link to this thread to bug report #421305 as you provide details why the included modules fail on Snow Leopard (they work fine on Leopard here) and how to fix it locally until new packages are available. Or even better - you could add a comment yourself?

Maybe the solution to packaging 0.47 for macosx is as 'easy' as

1. recompiling the included modules for Python 2.5 and Python 2.6 as universal binaries that include both intel i386 and x86-64 arch (if this is possible) or
2. adding an additional arch sub-folder for the bundled site-packages (x86-64) including newly compiled numpy and lxml modules for SL.

…in the meantime those who know how to install lxml and numpy locally (and how to edit the launch script) could follow your description here to get the extensions working on SL.

~suv

Yes both points mentioned in the previous post are spot on as the problem stems from the fact that the SL default X11.app is now a x86_64 bit based app and thusly the python site-packages (which are i386 only) turn up those errors about "mach-o but wrong architecture".

Either downgrade your X11.app (currently not possible as the SL X11.app from Xorg is not out yet) or compile lxml2 and numpy as "intel" (synonym by Python 2.6.4 configure for "i386 + x86_64") and stuff them into the Inkscape.app bundle as mentioned in the post before.

Or circumvent use of the app bundle included python stuff completely and just force Inkscape to use the default ones from Apple (which are "intel" by default) or any of the stuff your compiled as "intel".

Andre wrote:…as the problem stems from the fact that the SL default X11.app is now a x86_64 bit based app and thusly the python site-packages (which are i386 only) turn up those errors about "mach-o but wrong architecture".

I doubt that this is related to X11. AFAIU it is the default python binary from Apple that runs in 64bit mode and fails to load the 32bit libs from the bundled site-packages lxml and numpy.

Andre wrote:Or circumvent use of the app bundle included python stuff completely and just force Inkscape to use the default ones from Apple (which are "intel" by default) or any of the stuff your compiled as "intel".

There are no python modules lxml and numpy installed by Apple - that's why they are included in the inkscape package in the first place.