[Pythonmac-SIG] PyObjC/Py2App build problem
glassfordm at hotmail.com
Mon Jun 5 22:05:49 CEST 2006
Bob Ippolito wrote:
> On Jun 5, 2006, at 12:21 PM, Michael Glassford wrote:
>> Well, you're right about that; apparently I wasn't using it there.
>> However, I am using it most of the time, including earlier today
>> when I
>> said I got it working (I've verified that). What must have happened is
>> this: /usr/local/bin isn't permanently added to the beginning of my
>> because most of the real work I'm doing requires Python 2.3; instead,
>> when I want to work on the universal binary build, I open a new
>> window and add it manually. I must have forgotten to add it once.
> Out of curiosity, what are you doing that requires 2.3?
There's nothing in the code that requires Python 2.3, it was a policy
requirement: we've been officially using 2.3 because that's what we
started with, there was never a compelling reason to move to 2.4, and we
wanted to avoid code compatibility problems that could result if some
developers were using 2.3 and some were using 2.4. We will likely be
moving to 2.4 soon to use the universal binary versions of Python and
PyObjC now that they appear to be stabilizing.
>> So when I am correctly using the universal binary build of Python
>> (not 2.4.1, as Bob pointed out; sorry, I'm juggling too many things
>> today), is it necessary to set AUTO_UNIVERSAL = 1 in PyObjC's
> It's not necessary to set it if you're using a universal build of
> Python. It's effectively just a hack to get PyObjC (and only PyObjC)
> to build universally with Apple's Python 2.3.
OK, thanks. I thought I had read that somewhere but wasn't sure.
More information about the Pythonmac-SIG