On Jan 2, 2005, at 4:28 PM, Jack Jansen wrote:
>
> On 2-jan-05, at 4:40, Bob Ippolito wrote:
>>> +SCRIPT="""#!/bin/sh
>>> +export MACOSX_DEPLOYMENT_TARGET=10.3
>>> +exec %s "${@}"
>>
>> This script should check to see if MACOSX_DEPLOYMENT_TARGET is
>> already set. If I have some reason to set
>> MACOSX_DEPLOYMENT_TARGET=10.4 for compilation (say I'm compiling an
>> extension that requires 10.4 features) then I'm going to have some
>> serious problems with this fix.
>
> I was going to do that, but then I thought it didn't make any sense,
> because this script is *only* used in the context of Apple-provided
> Python 2.3. And setting MACOSX_DEPLOYMENT_TARGET to anything other
> than 10.3 (be it lower or higher) while compiling an extension for
> Apple's 2.3 is going to produce disappointing results anyway.
>
> But, if I've missed a use case, please enlighten me.
You're right, of course. I had realized that I was commenting on the
fixpython script after I had replied, but my concern is still
applicable to whatever solution is used for Python 2.4.1. Anything
lower than 10.3 is of course an error, in either case.
-bob
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4