Reading up on ways to run commands in a shell and capture output...
So I was looking at os.exec*() and that's not the correct thing here.
If I understand the docs correctly, the os.exec*() functions actually
end the calling program and replace it with the program called by
os.exec*() even as far as giving the new process the calling process's
PID:
"These functions all execute a new program, replacing the current
process; they do not return. On Unix, the new executable is loaded
into the current process, and will have the same process id as the
caller. Errors will be reported as OSError exceptions."
So from there, I found the commands module and getoutput() which
again, if I'm right, is supposed to run a command in a shell, and
return the output of that command a string.
commands.getoutput() is this:
def getstatusoutput(cmd):
"""Return (status, output) of executing cmd in a shell."""
import os
pipe = os.popen('{ ' + cmd + '; } 2>&1', 'r')
text = pipe.read()
sts = pipe.close()
if sts is None: sts = 0
if text[-1:] == '\n': text = text[:-1]
return sts, text
or at least it calls this function, and returns text, ignorint sts...
However, when I try using it, I get this:
>>> print commands.getoutput('dir')
'{' is not recognized as an internal or external command,
operable program or batch file.
>>>
Which looks like it's choking on the format of the "pipe = os.popen"
line, but that's just a guess... because this works:
p = os.popen('dir','r')
p.read()
p.close()
So what's the point of the commands module, or is that one that only
works in Linux, and not Windows? I can do what I want, I think, by
using os.popen(), but I wanted to know if there was a better way of
doing it.
Cheers,
Jeff
--
Jonathan Swift - "May you live every day of your life." -
http://www.brainyquote.com/quotes/authors/j/jonathan_swift.html
--
http://mail.python.org/mailman/listinfo/python-list
