Re: [Pyobjc-dev] Help getting Started with PyObjc2 and Leopard

[Bill B. <bb...@ma...>]

On Nov 29, 2007, at 5:14 PM, Barry Wark wrote:
> It can correctly build pyobjc2 (tests pass) on Leopard. For those of
> you in a similar position (wanting pyobjc2 but needing newer numpy
> etc.) give it a try. If this is a useful community resource, I'll work
> to put it in a more permanent location and/or do more regular builds
> (let me know if you find it useful). I haven't tested it except on our
> machines at work, which all have a similar configuration, so YMMV.

Thank you for building this!

For standalone packages -- including PyObjC -- you should be able to  
build said packages and install 'em via the standard mechanisms (I  
apologize -- looking back, I think I overstated the case originally).   
In particular, /Library/Python/2.5/site-packages/  is not populated  
and is intended for installing custom packages, including installing  
things more up to date than what is on the system.

Just don't overwrite system installed Python goop as various random  
applications may depend upon it.

If you build a custom Python, you'll need to install anything you need  
against that custom Python.

As well, if you ship an application and depend on Leopard stock  
installed Python Parts, I would highly recommend that you trim library  
path to not include /Library/Python as early as possible in your  
launch.   It'll prevent support heartache down the road.

b.bum