[issue1905] PythonLauncher not working correctly on OS X 10.5/Leopad

The Lawnmower man <[EMAIL PROTECTED]> added the comment: Sorry, but I still have the same problem as Kevin Walzer and I can't understand the solution proposed by Ronald Oussoren. Where is the patch? How can I install it? What I am supposed to do? Thank you very much! -- nosy: +thelawnmo

[issue1905] PythonLauncher not working correctly on OS X 10.5/Leopad

Georg Brandl <[EMAIL PROTECTED]> added the comment: No complaints were voiced, so I'm closing this. -- nosy: +georg.brandl status: pending -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue1905] PythonLauncher not working correctly on OS X 10.5/Leopad

Ronald Oussoren <[EMAIL PROTECTED]> added the comment: Python Launcher assumes that Terminal.app has a specific creator code, that's no longer true in Leopard. The code in doscript.m was already rather hackish, I've replaced it by a more modern way to use AppleEvents. I've committed a fix in r

[issue1905] PythonLauncher not working correctly on OS X 10.5/Leopad

Mark Dickinson added the comment: I can reproduce this in the trunk, on OS X 10.5.1/Intel: after a ./configure --enable-framework && make && sudo make altinstall ctrl-clicking on a simple python file on the Desktop and selecting OpenWith -> PythonLauncher fails to run the script and gives es

[issue1905] PythonLauncher not working correctly on OS X 10.5/Leopad

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 Pyt