Google says:
You need to use pythonw at the command line or the PythonLauncher
app to run wxPython apps, otherwise the app will not be able to
fully use the GUI display.
also:
I know that via the PythonLauncher we can automatically have scripts with a
.pyw extension run with pythonw.
Hope that helps.
John
Mike Taylor wrote:
One of the bugs I'm tracking down is to use the same
RunChandler and RunPython scripts for debug/release and also for the
various platforms and I've got it working for most of it except for a
.dmg install of Chandler.
What happens is that if I'm in a terminal inside the dmg bundle path:
~/Chandler_osx_foo.app/Contents/Resources/
and type
./release/RunChandler
I get the following:
This program needs access to the screen. Please run with 'pythonw',
not 'python', and only when you are logged in on the main display
of
your Mac.
now from the research I've done I have found that this is from the wx
startup code making a call to MacOS.WMAvailable() and that is returning
False. The odd part is that this is the same python binary that gets
run when you do this:
open ~/Chandler.foo.app
So obviously something is different about how RunPython is executing
the python binary but I haven't found out what yet.
any ideas?
---
Bear
Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org
[EMAIL PROTECTED]
http://code-bear.com
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
