views:

246

answers:

3

I am trying to create a pure-Python application bundle for a wxPython app. I created the .app directory with the files described in Apple docs, with an Info.plist file etc. The only difference between a "normal" app and this bundle is that the entry point (CFBundleExecutable) is a script which starts with the following line:

#!/usr/bin/env python2.5

Everything works fine except that the application name in the OSX menubar is still "Python" although I have set the CFBundleName in Info.plist (I copied the result of py2app, actually). The full Info.plist can be viewed here: http://tinyurl.com/32qgpjt

How can I change this? I have read everywhere that the menubar name is only determined by CFBundleName. How is it possible that the Python interpreter can change this in runtime?

Note: I was using py2app before, but the result was too large (>50 MB instead of the current 100KB) and it was not even portable between Leopard and Snow Leopard... so it seems to be much easier to create a pure-Python app bundle "by hand" than transforming the output of py2app.

+1  A: 

Change a key called LSHasLocalizedDisplayName in Info.plist to true, as in:

<key>LSHasLocalizedDisplayName</key>
<true/>

and then create a file in the executable bundle

foo.app/Contents/Resources/English.lproj/InfoPlist.strings

which has lines

CFBundleName="name in the menu bar";
CFBundleDisplayName="name in the Finder";
Yuji
Thanks for the answer!... But no luck :( I have also tried to add the CFBundleLocalizations key with no success.
gyim
ah, I forgot the semicolons in the `.strings` file. How is it now?
Yuji
I noticed the missing semicolons (it gave a warning), so it was not a problem. Here's the result: http://tinyurl.com/2wcqe9p
gyim
+1  A: 

It's sad that I'm answering my own question - again...

I finally found a solution: the "Build Applet.app" that comes with the Python developer tools is actually a pure-Python app bundle. It does the following:

  • a Python interpreter is placed (or linked) into the MacOS/ directory
  • the executable script (Foo.app/Contents/MacOS/Foo) sets up some environment variables and calls os.execve() to this interpreter.

The executable script looks like this (it is assumed that the entry point of the program is in Resources/main.py):

#!/System/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python
import sys, os
execdir = os.path.dirname(sys.argv[0])
executable = os.path.join(execdir, "Python")
resdir = os.path.join(os.path.dirname(execdir), "Resources")
libdir = os.path.join(os.path.dirname(execdir), "Frameworks")
mainprogram = os.path.join(resdir, "main.py")

sys.argv.insert(1, mainprogram)
pypath = os.getenv("PYTHONPATH", "")
if pypath:
    pypath = ":" + pypath
os.environ["PYTHONPATH"] = resdir + pypath
os.environ["PYTHONEXECUTABLE"] = executable
os.environ["DYLD_LIBRARY_PATH"] = libdir
os.environ["DYLD_FRAMEWORK_PATH"] = libdir
os.execve(executable, sys.argv, os.environ)
gyim
Nothing sad or wrong with answering your own question so long as you are right.
jathanism