PyObjC

So far I've gotten this error twice. The last time I rebooted and it  
went away (after trying some clean builds, etc...). This time it's  
still happening after a reboot. I'll have to flail around
and see if I can fix it. Any ideas?

Thanks,
-Scott

  <deleted stuff...>

     /usr/bin/env /Users/scottharris/Programming/CocoaNEC/setup.py  
py2app
Traceback (most recent call last):
   File "/Users/scottharris/Programming/CocoaNEC/setup.py", line 52,  
in ?
     setup_options = xcode.py2app_setup_options('app')
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/site-packages/PyObjC/PyObjCTools/XcodeSupport/ 
XcodeProj.py", line 99, in py2app_setup_options
     nibFiles = list(self.iterNIBFiles())
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/site-packages/PyObjC/PyObjCTools/XcodeSupport/ 
XcodeProj.py", line 38, in iterNIBFiles
     group = self.findGroup(name)
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/site-packages/PyObjC/PyObjCTools/XcodeSupport/ 
XcodeProj.py", line 25, in findGroup
     if group.name == groupName:
AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'
	AttributeError: 'PBXFileReference' object has no attribute 'name'

On Mar 21, 2006, at 6:55 PM, Scott Harris wrote:

> So far I've gotten this error twice. The last time I rebooted and  
> it went away (after trying some clean builds, etc...). This time  
> it's still happening after a reboot. I'll have to flail around
> and see if I can fix it. Any ideas?

Due to the lack of extensibility in Xcode, this stuff has to read the  
Xcode project file format directly.  It's not really guaranteed to be  
stable across versions, and normally we recommend building without  
Xcode if possible due to potential issues like this.  If you provide  
the actual xcodeproj bundle, someone might be able to help debug it.   
Otherwise you're on your own because the errors are worthless without  
the data that caused them.

-bob

OK, I guess I'll try to get rid of Xcode; at least I know where this  
is coming from now. It seems to happen randomly. Things were peachy  
for quite a while and then I added a comment to my obj-c source and  
this cropped up again.

So far I've only seen this in this project. Xcode has been nice to me  
so far.

Thanks,
-Scott
On Mar 21, 2006, at 8:04 PM, Bob Ippolito wrote:

>
> On Mar 21, 2006, at 6:55 PM, Scott Harris wrote:
>
>> So far I've gotten this error twice. The last time I rebooted and  
>> it went away (after trying some clean builds, etc...). This time  
>> it's still happening after a reboot. I'll have to flail around
>> and see if I can fix it. Any ideas?
>
> Due to the lack of extensibility in Xcode, this stuff has to read  
> the Xcode project file format directly.  It's not really guaranteed  
> to be stable across versions, and normally we recommend building  
> without Xcode if possible due to potential issues like this.  If  
> you provide the actual xcodeproj bundle, someone might be able to  
> help debug it.  Otherwise you're on your own because the errors are  
> worthless without the data that caused them.
>
> -bob
>
>

On 21-mrt-2006, at 23:03, Ronald Oussoren wrote:

> Whoops, it looks like I didn't pay attention. Apple seems to have  
> changed the calling conventions for OSX on Intel between WWDC'05  
> and the actual release of OSX. I haven't updated PyObjC's intel  
> support after WWDC, and now there are several bugs :-(
>
> I'll have to verify and fix the code in libffi-src and Modules/objc/ 
> {libffi_support.m,objc_support.m}. This will take some time, but  
> luckily our unittests should make it easy to tell when I've finished.

Changes seem to be fairly minor, although the remaining issues could  
well be more work than I'm expecting. If fixed a buglet w.r.t. the  
alignment of long long and double values (in both cases __alignof__ 
(type) says 8, while the actual value is 4), and I had to undo a  
patch that ensures the stack is 16-byte aligned.

This seems to fix issues with test_nsopenpanel, test_nsworkspace and  
guitest_graphics (all of these had a stacktrace that gave the  
impression that they couldn't open a connection to the windowserver,  
but actually by the stack alignment code mentioned above)

Both DotView and FieldGraph now function correctly, however only when  
I build with py2app -A. This is likely so because I'm using the stock  
py2app that knows nothing of universal binaries.

I'm not entirely convinced that libffi is now correct, AFAIK the  
assembly code that is at the core of closures doesn't know about  
stack alignment requirements. But so far it seems to work correctly.

Ronald

On 22-mrt-2006, at 21:53, Ronald Oussoren wrote:
>
> Changes seem to be fairly minor, although the remaining issues  
> could well be more work than I'm expecting.

That's what you get when you edit messages while debugging. The  
"remaining issues" I allude to were fixed before I had finished my  
previous message :-). The only thing left to do is making py2app  
aware of universal binaries. This should be fairly easy because  
others have already done the hard work, py2app-trunk contains  
suppport for universal binaries as does a patch that someone posted  
some time ago.

Before I do that however I'm going to merge patches from the python24- 
maint branch into python24-fat, in preparation for the release of  
python 2.4.3.

Ronald

On Mar 22, 2006, at 12:59 PM, Ronald Oussoren wrote:

>
> On 22-mrt-2006, at 21:53, Ronald Oussoren wrote:
>>
>> Changes seem to be fairly minor, although the remaining issues  
>> could well be more work than I'm expecting.
>
> That's what you get when you edit messages while debugging. The  
> "remaining issues" I allude to were fixed before I had finished my  
> previous message :-). The only thing left to do is making py2app  
> aware of universal binaries. This should be fairly easy because  
> others have already done the hard work, py2app-trunk contains  
> suppport for universal binaries as does a patch that someone posted  
> some time ago.

I went ahead and created a maintenance branch for py2app 0.2.x so we  
can go ahead and integrate those patches.  The trouble is finding  
them, I have too much mail and my machine is too slow so it's very  
painful to do anything with Mail.app.  Do you happen to have a copy  
of the patches or remember who contributed them?

-bob

On 22-mrt-2006, at 22:14, Bob Ippolito wrote:

>
> On Mar 22, 2006, at 12:59 PM, Ronald Oussoren wrote:
>
>>
>> On 22-mrt-2006, at 21:53, Ronald Oussoren wrote:
>>>
>>> Changes seem to be fairly minor, although the remaining issues  
>>> could well be more work than I'm expecting.
>>
>> That's what you get when you edit messages while debugging. The  
>> "remaining issues" I allude to were fixed before I had finished my  
>> previous message :-). The only thing left to do is making py2app  
>> aware of universal binaries. This should be fairly easy because  
>> others have already done the hard work, py2app-trunk contains  
>> suppport for universal binaries as does a patch that someone  
>> posted some time ago.
>
> I went ahead and created a maintenance branch for py2app 0.2.x so  
> we can go ahead and integrate those patches.  The trouble is  
> finding them, I have too much mail and my machine is too slow so  
> it's very painful to do anything with Mail.app.  Do you happen to  
> have a copy of the patches or remember who contributed them?

The patches were written by Ben Artin and should be here: <http:// 
periodic-kingdom.org/Public/pyobjc-trunk-universal-1.zip>.

Ronald

>
> -bob
>

I am able to build a new project with this alpha stuff!

But when I try to build my app, it chokes on webkit :-(

Did I do something wrong?

ValueError: '/Users/koen/Development/Foo/trunk/build/Foo.app/Contents/ 
Resources/Python/lib-dynload/WebKit/_WebKit.so' does not contain  
architecture ppc

On Mar 22, 2006, at 10:30 PM, Ronald Oussoren wrote:

>
> On 22-mrt-2006, at 22:14, Bob Ippolito wrote:
>
>>
>> On Mar 22, 2006, at 12:59 PM, Ronald Oussoren wrote:
>>
>>>
>>> On 22-mrt-2006, at 21:53, Ronald Oussoren wrote:
>>>>
>>>> Changes seem to be fairly minor, although the remaining issues  
>>>> could well be more work than I'm expecting.
>>>
>>> That's what you get when you edit messages while debugging. The  
>>> "remaining issues" I allude to were fixed before I had finished  
>>> my previous message :-). The only thing left to do is making  
>>> py2app aware of universal binaries. This should be fairly easy  
>>> because others have already done the hard work, py2app-trunk  
>>> contains suppport for universal binaries as does a patch that  
>>> someone posted some time ago.
>>
>> I went ahead and created a maintenance branch for py2app 0.2.x so  
>> we can go ahead and integrate those patches.  The trouble is  
>> finding them, I have too much mail and my machine is too slow so  
>> it's very painful to do anything with Mail.app.  Do you happen to  
>> have a copy of the patches or remember who contributed them?
>
> The patches were written by Ben Artin and should be here: <http:// 
> periodic-kingdom.org/Public/pyobjc-trunk-universal-1.zip>.
>
> Ronald
>
>>
>> -bob
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting  
> language
> that extends applications into web and mobile media. Attend the  
> live webcast
> and join the prime developer group breaking into this new coding  
> territory!
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Pyobjc-dev mailing list
> Pyobjc-dev@...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev