Comment 28 for bug 482993

a) incompatible architectures of module/python binary
Has anyone on Snow Leopard tried the solution proposed in comment #11 - using an Apple-provided environment variable to do the 'Selecting a specific python installation' magic with regard to version and architecture instead of editing $PATH (as proposed in comment #17)?

b) incompatible dylib versions loaded by modules/python binary
Also note that the fact that 'DYLD_LIBRARY_PATH' is no longer set in the launcher script potentially contributes to the error when trying to use a different python version installed with MacPorts: on OS X 10.5.8 Leopard extensions fail too [1], if using the bundled modules with python26 installed via MacPorts. The problem in this case is not 'different architecture' of the bundled modules and the python binary (both are i386) but a version conflict of the linked/loaded libraries (libxml2.2.dylib in this case). A possible solution for this (secondary) problem could be using the bundled modules only as fallback by adding the MacPorts path for site packages first in $PYTHONPATH, as outlined in comment #11. This would certainly be preferred to re-introducing 'DYLD_LIBRARY_PATH' (which is no longer needed since Inkscape 0.47).

[1] tested with latest bzr build from modevia as well as with local 0.47+devel builds (r9577) on OS X 10.5.8