On 9 Oct, 2007, at 23:11, Greg Ewing wrote:
Ronald Oussoren wrote:Is that the system supplied version of Python?No, it's my own installation of 2.3, but it's installed as a framework in /Library/Frameworks.My guess is MACOSX_DEPLOYMENT_TARGET: this is set in the> environment by distutils. I wondered about that -- I've noticed that with later Python versions, distutils linking commands *don't* work in the shell unless I set MACOSX_DEPLOYMENT_TARGET to 10.3 (it's not set at all in my shell environment by default). But the problem here is the other way around. I would have thought distutils would set it to something appropriate for the Python being used.
It is supposed to do that, but to be honest I don't remember if the code for that is present in the 2.3 tree and I'm too lazy to check the sources right now.
The deployment target does have an influence on how the compiler functions, which can explain when setting the target to a different value causes problems.
Any suggestions on how I can find out what setting of MACOSX_DEPLOYMENT_TARGET is being used by distutils, and how to make it use something different if it's not right?
In current versions of python this is read from config/Makefile in the standard library (that is /Library/Frameworks/Python.framework/ Versions/2.3/lib/python2.3/config/Makefile)
Ronald
-- Greg
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
