Re: PyObjC
Re: PyObjC
- Subject: Re: PyObjC
- From: Bill Bumgarner <email@hidden>
- Date: Tue, 5 Sep 2006 08:33:52 -0700
On Sep 5, 2006, at 1:12 AM, John C. Randolph wrote:
I thought Python and PyObjc were already present in Tiger. Why is
it necessary to include your own copies in your app?
Python 2.3.x is included with Tiger. PyObjC is not present at all.
The problem is that there are compatibility issues between dot
release of Python; code that worked in 2.3 may not work in 2.4 or
2.5. The compatibility issues are generally very minor, but *any*
compatibility issues are going to be a major headache for someone
shipping a commercial app. If Apple were to do software update that
addressed a critical security hole in Python and that involved a bump
from 2.3.5 to 2.4.x, it might break your app.
So, the easiest solution is to embed the Python interpreter (along
with PyObjC) into your app wrapper. Bob Ippolito put together
py2app, which does exactly this. It will also examine the dependency
graph of your code and strip out unreferenced modules. Beyond that,
py2app can also rewrite the mach-o headers of the embedded dylibs to
make them truly embedded.
b.bum
_______________________________________________
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
| References: | |
| | >PyObjC (From: "Daniel GQ Chong" <email@hidden>) |
| | >Re: PyObjC (From: Bill Bumgarner <email@hidden>) |
| | >Re: PyObjC (From: "John C. Randolph" <email@hidden>) |