[New-bugs-announce] [issue1905] PythonLauncher not working correctly on OS X 10.5/Leopad

Kevin Walzer report at bugs.python.org
Tue Jan 22 15:35:01 CET 2008


New submission from Kevin Walzer:

On Mac OS X 10.5 (Leopard), using Python 2.5.1, double-clicking on a 
Python script in the Finder does not produce the expected behavior, i.e. 
launch a terminal session and then execute the script. These errors are 
logged in the console:

1/22/08 9:28:56 AM Python Launcher[53692] doscript: Could not activate 
Terminal
 
1/22/08 9:28:56 AM Python Launcher[53692] doscript: AESend(activate): 
error -600
 
1/22/08 9:28:56 AM Python Launcher[53692] Exit status: -600
 
1/22/08 9:28:56 AM com.apple.launchd[118] ([0x0-
0x434434].org.python.PythonLauncher[53692]) Stray process with PGID 
equal to this dead job: PID 53694 PPID 1 Terminal 

I did not observe these behaviors on OS X 10.4.

----------
components: Macintosh
messages: 61506
nosy: wordtech
severity: major
status: open
title: PythonLauncher not working correctly on OS X 10.5/Leopad
type: behavior
versions: Python 2.5

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1905>
__________________________________


More information about the New-bugs-announce mailing list