Re: psexec and os.popen help
[EMAIL PROTECTED] wrote:
> popen3 did the trick.
Use the modules "subprocess" ... it solves many problems, including
the problem of too many similar functions. :-)
These functions (execl, execv, popen, popen2, popen3, ...) are relicts
from C and very unpythonic. It's IMHO always a better programming style
to use "subprocess".
Greets,
Volker
--
Volker Grabsch
---<<(())>>---
\frac{\left|\vartheta_0\times\{\ell,\kappa\in\Re\}\right|}{\sqrt
[G]{-\Gamma(\alpha)\cdot\mathcal{B}^{\left[\oint\!c_\hbar\right]}}}
--
http://mail.python.org/mailman/listinfo/python-list
Re: psexec and os.popen help
popen3 did the trick. Thanks Jeff Gercken -- http://mail.python.org/mailman/listinfo/python-list
psexec and os.popen help
I'm trying to wrap a psexec command in a python script so I can capture
the results and generate an exception report. The problem I'm having is
that when I use x = os.popen("command") to do it, it runs, but the
content of x is empty. I know there should be output sent to it,
because when I run the command from the DOS prompt, it shows it. I
don't have this problem when wrapping other PSTools. Has anyone else
had this problem, or can someone try it and verify that it works, then
show me there work? I really appreciate it. Its been a late night.
Thanks
Dennis
--
http://mail.python.org/mailman/listinfo/python-list
