Issue 1666952: terminalcommand doesn't work under Darwin (original) (raw)

Created on 2007-02-23 10:29 by jneb, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg31319 - (view)	Author: Jurjen N.E. Bos (jneb) *	Date: 2007-02-23 10:29
The "terminalcommand" library doesn't work under Darwin. It raises an obscure AppleScript error that I can't figure out. I made a tiny library that gives roughly the same API, but starts applications fine under Darwin (10.2 and up). It works using the osascript command, but Jack can probably get it too work using OSA directly :-) Quotes, spaces and backslashes are handled properly. I would recommend to extend terminalcommand to incorporate this code in the Darwin case, assuming that you still want to support OS9.
msg31320 - (view)	Author: Jurjen N.E. Bos (jneb) *	Date: 2007-02-23 10:31
O yes: forgot to mention: The bug is for Mac only, any version of Python, OS X and up.
msg31321 - (view)	Author: Ronald Oussoren (ronaldoussoren) *	Date: 2007-07-12 05:38
Are you using an Intel or PPC mac?
msg31322 - (view)	Author: Jurjen N.E. Bos (jneb) *	Date: 2007-07-12 10:29
It is an Intel MacBook Pro. I though I ran 10.4.9 at the time, but I guess that is not an issue.
msg66122 - (view)	Author: Ronald Oussoren (ronaldoussoren) *	Date: 2008-05-02 22:09
I cannot reproduce this issue with Python 2.5 or 2.6. There was a bug in terminalcommand when running on Leopard, I fixed that earlier tonight.