This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients davin, kapilt, ned.deily, pitrou, ronaldoussoren
Date 2018-06-04.21:39:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
{Note: this is not particularly relevant to the issue here.)

> In the long run the macOS installers should be build using the latest SDK [...] That's something that would require some effort though to ensure that the resulting binary still works on older versions of macOS

I agree that being able to build with the latest SDK would be nice but it's also true it would require effort on our part, both one-time and ongoing, at least for every new macOS SDK release and update to test with each older system.  It would also require that the third-party libraries we build for an installer also behave correctly.  And to make full use of it, third-party Python packages with extension modules would also need to behave correctly.  I see one of the primary use cases for the macOS installers as being for Python app developers who want to provide apps that run on a range of macOS releases.  It seems to me that the safest and simplest way to guarantee that macOS Pythons fulfill that need is to continue to always build them on the oldest supported system.  Yes, that means that users may miss out on a few features only supported on the more recent macOS releases but I think that's the right trade-off until we have the resources to truly investigate and decide to support weak linking from current systems.
Date User Action Args
2018-06-04 21:39:10ned.deilysetrecipients: + ned.deily, ronaldoussoren, pitrou, davin, kapilt
2018-06-04 21:39:10ned.deilysetmessageid: <>
2018-06-04 21:39:10ned.deilylinkissue33725 messages
2018-06-04 21:39:10ned.deilycreate