[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.3" but "10.5" during configure

[Sridhar Ratnakumar]

Sridhar Ratnakumar <sridharr at activestate.com> added the comment:

On 2010-08-17, at 9:01 PM, Ronald Oussoren wrote:

> I now understand why my script fails, and it is caused by this issue.
> 
> The sysconfig.py code has another major issue: the use of os.putenv. This changes the environment, without changing os.environ. The use of os.putenv should be replaced by setting keys in os.environ to make it easier to discover that changes have been made.
> 
> Even that is no good: setting the environment variable should only be done in distutils to ensure that the right build environment is used. It should not be set globally where it will affect code that it was never intended to affect.

I agree that environment variable should only be affected during distutils build, and not globally.

I now recall debugging this issue (with 2.7 alpha/beta, I guess) and arriving at the same confusion.

> BTW. Sridhar: could this be the reason you cannot find the correct reproduction steps for this?  Do you use a build script that is writting in python and run with a copy of python where sysconfig.get_config_var('MACOSX_DEPLOYMENT_TARGET') returns '10.3'?

Yes, but I am not entirely sure if that copy of python returned 10.3, and I no longer have that copy ... as I've been upgrading 2.6 and 2.7 pretty often in our two Mac build machines.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9516>
_______________________________________