Re: [Pyobjc-dev] py2app builds fail leopard codesign integrity checks

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

On Nov 20, 2007, at 10:30 AM, Kevin Walzer wrote:
> I don't quite understand the problem here, but do these issues mean  
> it's a Bad Idea to use the Apple-shipped py2app and PyObjC? I was  
> planning on doing this when I upgraded to Leopard.

Apple-shipped PyObjC is fine unless you need the post 2.0 bugfixes  
that Ronald has committed.   If you are using the Xcode based project  
templates, this is all a non-issue as they do not use py2app (but  
you'll have to add a 'copy files' or 'shell script' build phase to add  
any python specific non-standard resources to your app's resources).

It also sounds like the py2app executable stubs should *not* have been  
signed when Leopard was built.   I'll have to look into that.

b.bum