Clickable (wx)python app in OS X

[PhysicsGenius]

AAAAARRRRRRRRGGHGHGHGHGHGHGHGHGH!!!!!! I hate Macs.

I have a wxPython program. It runs fine on OS X when I launch it from
the Terminal ("pythonw appname.py") . The user wants to be able to
click it. Two main suggestions on the Internet, neither of which
works:

1) "Use Platypus" So I download it, upgrade Stuffit, install both,
figure out how to use it, create an app....and it doesn't work for
graphical apps. Nice to know, thanks for telling me ahead of time!

2) "Just associate .py files with PythonInterpreter". Sounds easy!
So I navigate to appname.py, Get Info, Open With, navigate to
PythonInterpreter....WhereTF is "PythonInterpreter"? Not on the OS X
system anywhere and Google only finds a Python module.

So, how do I create a clickable icon that will launch my wxPython
program?

 

[Chris McD]

AAAAARRRRRRRRGGHGHGHGHGHGHGHGHGH!!!!!! I hate Macs.

I have a wxPython program. It runs fine on OS X when I launch it from
the Terminal ("pythonw appname.py") . The user wants to be able to
click it. Two main suggestions on the Internet, neither of which
works:

1) "Use Platypus" So I download it, upgrade Stuffit, install both,
figure out how to use it, create an app....and it doesn't work for
graphical apps. Nice to know, thanks for telling me ahead of time!

2) "Just associate .py files with PythonInterpreter". Sounds easy!
So I navigate to appname.py, Get Info, Open With, navigate to
PythonInterpreter....WhereTF is "PythonInterpreter"? Not on the OS X
system anywhere and Google only finds a Python module.

So, how do I create a clickable icon that will launch my wxPython
program?

Well you are opening it with pythonw so why not associate *.py with
pythonw or python?

Chris

 

[PhysicsGenius]

Well you are opening it with pythonw so why not associate *.py with
pythonw or python?

Chris

I was pretty sure this was impossible, but I may
have done it. For anyone else as frustrated as I
was (and still am, kinda): I associated .py with
/System/Library/Frameworks/Python.framework/Resources/PythonLauncher.
It still brings up a Terminal window, but at
least the app launches from a click.

Mac OS X: It Just Works (poorly)

 

[has]

So, how do I create a clickable icon that will launch my wxPython
program?

http://pythonmac.org/wiki/BundleBuilder

 

[Alex Martelli]

AAAAARRRRRRRRGGHGHGHGHGHGHGHGHGH!!!!!! I hate Macs.

Just the perfect approach to get any help whatsoever from those of us
who don't.

*PLONK*.


Alex

 

[Ronald Oussoren]

I was pretty sure this was impossible, but I may have done it. For
anyone else as frustrated as I was (and still am, kinda): I associated
.py with
/System/Library/Frameworks/Python.framework/Resources/PythonLauncher.
It still brings up a Terminal window, but at least the app launches
from a click.

If you asked your question on the pythonmac SIG you'd have gotten your
answer a lot sooner

The best way to build a double-clickeable application on OSX is by
building an .app bundle that contains your application. One way to do
this is using bundlebuilder:

# buildapp.py
from bundlebuilder import buildapp

buildapp(
name = "My Application",
mainprogram = "TableModel.py",
resources = ["English.lproj"],
nibname = "MainMenu",
)
# end of buildapp.py

You can now run 'python buildapp.py build' to create the application
bundle, run 'python buildapp.py' to see some more options.

Mac OS X: It Just Works (poorly)

No, it works differently

 

[Greg Ewing]

http://pythonmac.org/wiki/BundleBuilder

You could also try creating a bundle by hand. I tried that
as an experiment recently, and I got it to work. From memory,
all you need is a directory structure that contains

NameOfApp.app/Contents/MacOS/NameOfApp

where the final NameOfApp is the executable. This can be
a Python script with a #! line that invokes the appropriate
interpreter (python or pythonw). Any other modules that it
needs can be put in the MacOS directory alongside it.

Another way is to use AppletBuilder to create a "skeleton"
bundle from your main .py file, and then manually add other
required modules to the MacOS directory. That will give
you command line emulation, ability to give it a nice icon,
etc.