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 emptysquare, gvanrossum, martin.panter, ned.deily, ronaldoussoren, yselivanov
Date 2016-02-10.03:25:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree that the approach in "try 2" is fine and the runtime check in "try 3" is overkill.  While it is possible to do so, we've never really supported building on an OS X release n for release m, where m < n, without using the m SDK on n (and in particular for m=10.4) in which case the "try 2" test should work correctly.  Ronald, what do you think?
Date User Action Args
2016-02-10 03:25:35ned.deilysetrecipients: + ned.deily, gvanrossum, ronaldoussoren, martin.panter, yselivanov, emptysquare
2016-02-10 03:25:35ned.deilysetmessageid: <>
2016-02-10 03:25:35ned.deilylinkissue25924 messages
2016-02-10 03:25:35ned.deilycreate