OS X & Python 3: Behavior while executing bash command in new terminal?

Question

I've seen similar questions (e.g. Running a command in a new Mac OS X Terminal window ) but I need to confirm this command and its expected behavior in a mac (which I don't have). If anyone can run the following in Python 3 Mac:

import subprocess, os
def runcom(bashCommand):
     sp = subprocess.Popen(['osascript'], stdin=subprocess.PIPE, stderr=subprocess.PIPE)
     sp.communicate('''tell application "Terminal"\nactivate\ndo script with command "{0} $EXIT"\nend tell'''.format(bashCommand))

runcom('''echo \\"This is a test\\n\\nThis should come two lines later; press any key\\";read throwaway''')
runcom('''echo \\"This is a test\\"\n\necho \\"This should come one line later; press any key\\";read throwaway''')
runcom('''echo \\"This is testing whether I can have you enter your sudo pw on separate terminal\\";sudo ls;\necho \\"You should see your current directory; press any key\\";read throwaway''')

Firstly, and most basically, is the "spawn new terminal and execute" command correct? (For reference, this version of the runcom function came from this answer below, and is much cleaner than my original.)

As for the actual tests: the first one tests that internal double escaped \\n characters really work. The second tests that we can put (unescaped) newlines into the "script" and still have it work just like semicolon. Finally, the last one tests whether you can call a sudo process in a separate terminal (my ultimate goal).

In all cases, the new terminal should disappear as soon as you "press any key". Please also confirm this.

If one of these doesn't work, a correction/diagnosis would be most appreciated. Also appreciated: is there a more pythonic way of spawning a terminal on Mac then executing a (sudo, extended) bash commands on it?

Thanks!

score 1 · Answer 1 · answered Sep 24 '11 at 02:43

1

I don't have Python 3, but I edited your runcom function a little and it should work:

def runcom(bashCommand):
    sp = subprocess.Popen(['osascript'], stdin=subprocess.PIPE, stderr=subprocess.PIPE)
    sp.communicate('''tell application "Terminal"\nactivate\ndo script with command "{0} $EXIT"\nend tell'''.format(bashCommand))

answered Sep 24 '11 at 02:43

icktoofay

126,289
21
250
231

This looks a lot cleaner. I'm going to edit that into the original data request! Thanks! – scarlet Sep 24 '11 at 02:58

score 1 · Accepted Answer · answered Sep 25 '11 at 00:58

[...] its expected behavior [...]

This is hard to answer, since those commands do what I expect them to do, which might not be what you expect them to do.

As for the actual tests: the first one tests that internal double escaped \n characters really work.

The \\n with the doubled backslash does indeed work correctly in that it causes echo to emit a newline character. However, no double quotes are emitted by echo.

The second tests that we can put (unescaped) newlines into the "script" and still have it work just like semicolon.

That works also.

Finally, the last one tests whether you can call a sudo process in a separate terminal (my ultimate goal).

There is no reason why this should not work also, and indeed it does.

In all cases, the new terminal should disappear as soon as you "press any key". Please also confirm this.

That will not work because of several reasons:

read in bash will by default read a whole line, not just one character
after the script you supply is executed, there is no reason for the shell within the terminal to exit
even if the shell would exit, the user can configure Terminal.app not to close a window after the shell exits (this is even the default setting)

OS X & Python 3: Behavior while executing bash command in new terminal?

2 Answers2