On Tue, Dec 8, 2009 at 14:44, Jerry Hill wrote:
> At the very top of http://docs.python.org/library/commands.html it
> says "Platforms: Unix", so yes, it's Unix-only.
That sound you hear is me beating my head against the table now...
sigh... I was too wrapped up in reading the actual code to not
On Tue, Dec 8, 2009 at 2:31 PM, J wrote:
>
> So what's the point of the commands module, or is that one that only
> works in Linux, and not Windows?
At the very top of http://docs.python.org/library/commands.html it
says "Platforms: Unix", so yes, it's Unix-only.
> I can do what I want, I think,
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 a
