
Meh...I hate it when tools download stuff without me noticing. Honestly, a separate 10.6 build would work well. Plus, if a new Clang versions includes some awesome feature that could make Python builds better, you'd be able to take advantage of it better. On Mon, Sep 16, 2013 at 2:56 PM, Bill Janssen <janssen@parc.com> wrote:
Russell E. Owen <rowen@uw.edu> wrote:
In article <B3293155-E4D5-4389-A555-C31BC49CE539@gmail.com>, Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
The most recent Developer Tools for 10.8 and 10.7 systems, Xcode 4.6.x, have a mature clang but do not provide a 10.6 SDK. Even with using an SDK, it's still possible to end up inadvertently linking with the wrong versions of system libraries. We have been burned by that in the
On Sep 14, 2013, at 1:32 PM, Ned Deily <nad@acm.org> wrote: past.
I think we should offer a separate Mac build just for 10.6 (much like we do for the 32-bit PPC option for 10.5).
If Apple drops support for gcc in 10.9 I guess we have to go this route,
Could go the Sage route -- Sage first checks for an up-to-date version of gcc, and downloads it and builds it for its own use if necessary.
Bill
but please be careful. Every time you add a new version of python for MacOS X it means that folks providing binary installers (e.g. for numpy) have to provide another binary, and folks using those installers have another chance of picking the wrong one.
If you do make a 10.6-only installer, what is the minimum version of MacOS X the modern compiler would support? 10.7 gives a more measured upgrade path, but 10.8 gives a better compiler.
-- Russell
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/bill%40janssen.org
Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com
-- Ryan