Comment 9 for bug 819209

> Not sure. If that were the case, would one expect
> extensions in 0.48.1 to already work in 10.7?

No. The file your installer patches in current Inkscape packages only sets $VERSIONER_PYTHON_PREFER_32_BIT but does not require a specific the python version ($PATH is set to run 'python' from '/usr/bin'). [1]

With Python 2.7.1 new in Lion as default python version, Apple has probably no reason (legacy) to include a 32bit version in the universal binary (Lion is full 64bit, and Python 2.7 was never shipped with a 32bit-only version of Mac OS X). Thus I assume that on Lion, setting $VERSIONER_PYTHON_PREFER_32_BIT alone fails if the python version is not limited to an earlier python version which includes 32bit binaries due to legacy reasons (using $VERSIONER_PYTHON_VERSION).

> I'm willing to run any tests that you can specify here.

1) Could you look up the man page for python ('man python' in the terminal) whether on OS X Lion it still supports the same environment variables as on Snow Leopard? [2] As mentioned above, I can't find the python man page for OS X Lion online.
2) For testing, could you use the diff I attached in comment #7 to change an _original_ version of 'Inkscape.app/Contents/Resources/bin/inkscape' of 0.48.1 or 0.48.2 (i.e. not one patched by your installer!) and test on OS X Lion if Inkscape then launches Python 2.6 in 32bit mode (using e.g. the debug extension from bug #482993)?

[1] <http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_48_BRANCH/view/head:/packaging/macosx/Resources/bin/inkscape#L26>
    <http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_48_BRANCH/revision/9719>
[2] <http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man1/python.1.html>