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 debohman, ned.deily, ronaldoussoren
Date 2018-04-15.20:30:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523824213.07.0.682650639539.issue24414@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for your suggested patch and my apologies for not replying sooner.  For Python 2.7.15, we have done some housecleaning of old macOS support issues and, as part of ee8e4b61d6181f5bfadf6ee3d229f0ebda8a6ae9 for Issue32726, I have backported the deployment target setting behavior from 3.x, i.e. the deployment target on current systems is now set to the build system's OS level unless overridden by MACOSX_DEPLOYMENT_TARGET= on the configure command or as an environment variable.  So the previous behavior can be forced by:

./configure MACOSX_DEPLOYMENT_TARGET=10.4

As you noted, using a proper value for the deployment target allows things like using the system libedit readline support and standard library support for more recent system calls.
History
Date User Action Args
2018-04-15 20:30:13ned.deilysetrecipients: + ned.deily, ronaldoussoren, debohman
2018-04-15 20:30:13ned.deilysetmessageid: <1523824213.07.0.682650639539.issue24414@psf.upfronthosting.co.za>
2018-04-15 20:30:13ned.deilylinkissue24414 messages
2018-04-15 20:30:12ned.deilycreate