Russell E. Owen <[email protected]> wrote: > In article <[email protected]>, > Raymond Hettinger <[email protected]> wrote: > > > On Sep 14, 2013, at 1:32 PM, Ned Deily <[email protected]> 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 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 > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/bill%40janssen.org _______________________________________________ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
