There's a related issue, using the 10.6 SDK. This one is over a year old, but as far as I know still has no solution.
Xcode 4.4+ have no 10.6 SDK. This doesn't actually stop you from building extensions; they just falls back to building for your machine when it can't find the SDK. But that means you can't build binary distributions of your extensions (or py2app executables, etc.). So, if you want to create useful Python binaries, you have to either keep an old development machine around, or build Python yourself. >From a quick test, building Python to use a later SDK, but >macosx-version-min=10.6, seems to work. As I mentioned in my previous email, I >don't actually have a 10.6/3.2 machine to test, but here's what _did_ work: >Building Python on a 10.7.5/4.6.2 machine with the 10.8 SDK and >macosx-version-min=10.6. Install the result on a 10.8.5/5.0.1 machine. Build >an extension on the 10.8 machine. Install the extension on the 10.7 machine. >Use it. However, I haven't done much testing. And I've definitely seen other cases where setting macosx-version-min lower than the SDK doesn't work, despite assurances from Apple that the bugs I'm seeing are impossible, so I'm not sure how far to trust this. _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
