PyObjC on OS X on Intel
PyObjC on OS X on Intel
- Subject: PyObjC on OS X on Intel
- From: Nicko van Someren <email@hidden>
- Date: Tue, 7 Jun 2005 14:09:44 +0100
On 7 Jun 2005, at 12:51, Luc Heinrich wrote:
On 7 juin 05, at 13:24, Nicko van Someren wrote:
Presumably it should all "just work". PyObjC does not contain any
assembly code that I'm aware of and the underlying Python is
endian independent, so at least in theory it should just compile
as a fat binary and run.
"Python on Mac OS X for Intel is not going to be a seamless
transition."
<http://bob.pythonmac.org/archives/2005/06/06/python-on-mac-os-x-x86>
OK, I take back the comment about it "just work"ing. I didn't
realise that PyObjC was such a mess architecturally. That said, of
the five points he raises three are really "we don't know because
it's not published yet" type of problems, one will be tedious work
and one, the issue with autoconf, is something that is going to be
faced by a great number of people and I suspect an Open Source
solution will emerge[*] as this becomes relevant to more people.
Nicko
[*] I think that Open Source advocates believe that OS solutions
emerge to problems in the same way that Free Market advocates believe
that The Market correctly balances the economy. Evidence suggests
that neither supposition is entirely correct, but it seems to work as
a rule of thumb. YMMV.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden