On 10/24/13 7:50 PM, Andrew Barnert wrote:
What should users be doing until this is fixed?
Build Python yourself, in my view. Python is one of the easiest scripting languages to build. And once you do that, building extensions is just a matter of sudo easy_install foo.
What we're seeing here is a conflict between Python's unfortunate insistence on using the same compiler toolchain for the main interpreter and any compiled extensions, and Apple's remorseless dropping of stuff it no longer supports.
I don't believe there is a way to resolve this conflict. Eventually clang will have been the standard compiler for three or four versions of OS X, and that will resolve it. Until then there will be several different compilers in the wild--gcc-4.2, gcc-llvm, and clang, and we'll have these headaches with incompatibility.
Ronald and Ned can speak in a more official capacity, as the maintainers, but that's my two cents.
--Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
