Re: [Pyobjc-dev] NSSet valueForKey: breaks when using py2app
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2005-11-03 08:34:18
|
On 3-nov-2005, at 0:47, Bill Bumgarner wrote: > On Nov 2, 2005, at 3:11 PM, Bob Ippolito wrote: >> That's probably it. It's an interesting issue -- I wonder what >> the best solution to this would be. Bill should probably speak up >> here, he'd know more about this garbage link-time behavior change >> stuff :) > > Oh.... that'd be bad. If you are linking against the Panther > Foundation, then the Tiger Foundation is going to ensure Panther- > esque behavior. There is compatibility-fu that guarantees > binaries linked on Panther will run in a bug-for-bug identical > environment as to where they were built. Hmm. I'll have to rethink one of my plans for PyObjC then. I want to restructure PyObjC in such a way that we can ship one binary package that will work on Panther and Tiger. That's not going to work if PyObjC linked on Panther behaves differently from one linked on Tiger. Ronald > > Rebuilding the bootstrap on Tiger will solve the problem. NSSet's > KVC behaviors were extended significantly in Tiger, IIRC. > > b.bum |