[Chandler-dev] 0.7.4-rc1 pre-test images available

Grant Baillie grant at osafoundation.org
Fri Jan 25 16:34:46 PST 2008


On 25 Jan, 2008, at 15:22, Robin Dunn wrote:

> Jared Rhine wrote:
>
>> Please report any successes or failures you may have.  If things  
>> are looking good, I'll proceed to a more traditional RC1  
>> announcement.
>
> The application bundle for Leopard is showing "Python" in the  
> application menu title instead of "Chandler".  It looks to me like  
> all the necessary things are in the Info.plist file, so I'm not sure  
> why it isn't showing "Chandler"...  My guess is that is has  
> something to do with either the double exec from the ChandlerApp  
> shell script, (ChandlerApp --> RunPython --> Python) and/or that it  
> is resulting in an exec of the Python bundle located *outside* of  
> the Chandler app bundle.  (So the menu is taking the name from that  
> bundle instead of the chandler bundle.)
>
> To test this I replaced the bundle's Contents/MacOS/ChandlerApp  
> script with a Python script (attached) that does basically what the  
> RunPython script does.  That does fix the app name on the menu, but  
> I expect that some more testing should be done to make sure I didn't  
> miss anything.

Yes, I think you're exactly right here.

> IIRC the bundle for Tiger that includes its own Python gets around  
> this problem by using a custom Info.plist in the Python bundle.   
> This same approach could be used in that app bundle and it would be  
> able to not need to rely on that hack anymore.  It would just need  
> to run the script with the other python.

Right, in general there isn't a way to put the custom Tiger python  
executable in the #! line. But it should work to execve that at the  
end of the script.

--Grant




More information about the chandler-dev mailing list