On 11/1/07, Christopher Barker <[EMAIL PROTECTED]> wrote: > Robert Kern wrote: > > It's unlikely they are going to. If they put that stuff there, it's because > > they > > are using it for something, not as an (in)convenience to you. I don't > > recommend > > using the Python.framework in /System for anything except for distributing > > lightweight .apps. > Hence Roberts solution: treat the Apple Python as a system only tool, > only to be added to by Apple themselves. I guess that's OK, but it's > really silly that it has to be that way.
It's not entirely silly. This has been the advice given to app developers on this list and the PyObjC list for years now. It's nice to have a better system Python for quick scripts, but it's still the System Python. It's Apples, for their stuff that uses Python. And it is specific to OS 10.5. If you use it to build your app, your app is pretty much guaranteed not to work when someone tries to run it on 10.6, etc. Maybe they have changed how py2app works in 10.5, but the old behavior was to embed Python into your app, UNLESS it was the system python. Unless there is evidence to the contrary (I don't have Leopard yet), I assume that is still true. The old advice still holds: For building apps, install your own framework build of Python, put it first in your path, and add any libraries you require to it. Then you have control over what goes into your app, not Apple. --Dethe _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
