Thanks to all who have replied with information, and especially to Bob for pointing me to a location where I can find a bunch of recent universal binary builds of python components. I have not found a link to this page on the Internet before, hopefully your post will help search engines find it.
Here is a bit of extra information, what I got to work and the question I still have: - I am a recent Mac convertee (what took me so long?), and I am setting up PyObjC on my iMac for the first time - I originally tried PyObjC v1.3.7, the latest package I found at http://pyobjc.sourceforge.net/ and of course that did not work With the help of the wonderful people on this list: - I have checked out the latest PyObjC using subversion (here comes my CVS-to-subversion conversion) and built it with Python 2.3.5, which comes pre-installed with OS X 10.4 I have managed to do a build, install the package, and than used XCode to build a sample PyObjC application - awesome. Now, are there any side affects of switching the system over to use python 2.4? I have played around a bit with installing MacPython 2.4 (once again thanks to Bob's link) but I found that XCode picks up / bin/python (which is 2.3.5) and not /usr/local/bin/python, which is where MacPython 2.4 installs a link to its binary. Being new to Mac I must ask - is it safe to just point python binary links in /bin to match those found in /usr/local/bin or should I be weary of some side affects? Thank You, Marcin On 14-May-06, at 1:43 PM, Bob Ippolito wrote: > > On May 14, 2006, at 5:31 PM, Ronald Oussoren wrote: > >> >> On 14-mei-2006, at 14:21, Marcin Komorowski wrote: >> >>> Does anyone know what that status is of porting PyObjC to run on the >>> new Intel Macs? >>> >>> I know that there has already been some amount of work done, but my >>> attempts to run it on the new platform have failed. >>> >>> Should I be trying to be digging deeper into what I might be doing >>> wrong, or is the port not complete? >> >> The current version in subversion should work correctly, PyObjC's >> unittests also run the unittests for libffi and all except two of >> those pass. The tests that fail have to do with very small structures >> (1 or 2 bytes in size) and those aren't used in Cocoa APIs. >> >> If you do find something that doesn't work as expected in PyObjC or >> py2app I'm definitely interested to here about it. A small program >> that demonstrates the problem would make it easier to reproduce any >> problems, and hence increase the likelyhood of timely fixes. > > The binary package at http://pythonmac.org/packages/py24-fat/ is > recent too, I updated it a day or two ago. > > -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig