[Pythonmac-SIG] Problems with PythonLauncher on Leopard

[Kevin Walzer]

I've noticed strange behavior with PythonLauncher on Leopard (I'm using 
the standard build of MacPython 2.5.1).    The expected behavior with 
PythonLauncher is that when I double-click on a Python script, a 
Terminal window will launch and cd to the script's working directory, 
and then Python will run the script.

What's happening now is that PythonLauncher opens a Terminal window, but 
it does not change the working directory to the script's directory, and 
Python never runs the script.

Here's some output from Console:

12/19/07 10:31:16 AM Python Launcher[1467] doscript: Could not activate 
Terminal

12/19/07 10:31:16 AM Python Launcher[1467] doscript: AESend(activate): 
error -600

12/19/07 10:31:16 AM Python Launcher[1467] Exit status: -600

12/19/07 10:31:16 AM com.apple.launchd[146] 
([0x0-0x9c09c].org.python.PythonLauncher[1467]) Stray process with PGID 
equal to this dead job: PID 1469 PPID 1 Terminal
12/19/07 10:31:32 AM com.apple.launchd[1] (com.apple.dyld) Throttling 
respawn: Will start in 60 seconds

I can obviously work around this by running everything from the 
command-line, i.e. cd myscriptpath && python myscript.py, but 
PythonLauncher is supposed to do this for me. Has anyone else observed 
this kind of behavior?

--Kevin

-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com