Ned Deily <n...@acm.org> added the comment: For people searching the bug tracker, I've modified the title of the issue to make it clearer that there is a problem here on OS X 10.6 Snow Leopard with multiple architecture builds.
As Ronald mentions above, the effect of using the pythonw "launcher" on 10.6 as it currently stands is to always prefer x86_64 (64-bit) over i386 (32-bit) when both are available. arch -i386 only forces the launcher to run as 32-bit; the execv runs the interpreter in 64-bit mode (if available). To get a multi-arch (32/64) interpreter to run in 32- bit, one workaround is to arch -i386 directly to the interpreter binary in the framework app bundle, typically: /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/C ontents/MacOS/Python But then, presumably, the GUI functionality no longer works. A more robust workaround would be to build a 32-bit-only Python (but ensure that -arch is forced on the build - see Issue7184). ---------- nosy: +ned.deily title: use different mechanism for pythonw on osx -> use different mechanism for pythonw on osx: universal builds always run 64-bit on OS X 10.6 type: feature request -> behavior _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6834> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
