On Mon, 30 Aug 2010 10:24:26 -0400, python wrote:
>> Kudos for avoiding shell=True
>
> My understanding is that the only time one needs to use shell=True is
> when they are 'executing' a non-executable file whose executable must be
> discovered via file association rules? Does that sound accurate
On 30/08/2010 3:24 PM, pyt...@bdurham.com wrote:
My understanding is that the only time one needs to use shell=True is
when they are 'executing' a non-executable file whose executable must be
discovered via file association rules? Does that sound accurate?
I'm not entirely sure what you mean by
Hi Chris,
> It's a bug: http://bugs.python.org/issue1170
Thanks for pointing out the shlex bug. My concern was that shlex had
Windows specific Unicode limitations because of the way the Windows
shell so poorly supports unicode output.
> Kudos for avoiding shell=True
My understanding is that the
On Mon, Aug 30, 2010 at 6:54 AM, wrote:
> Python 2.6/Windows: shlex.split() does not support unicode strings. Is this
> simply a limitation of the current shlex implementation or is this an
> intentional design decision that reflects the behavior of how the Windows
> shell supports unicode values
Python 2.6/Windows: shlex.split() does not support unicode
strings. Is this simply a limitation of the current shlex
implementation or is this an intentional design decision that
reflects the behavior of how the Windows shell supports unicode
values?
Specifically, it doesn't appear that subprocess
Werner F. Bruhin wrote:
I am trying to use subprocess - it basically works but.
command = 'ping ' + '-n '+ str(count) + ' -l ' +
str(size) + ' ' + str(node)
print command
p = subprocess.Popen(command, stdin=subprocess.PIPE,
Werner F. Bruhin wrote:
I am trying to use subprocess - it basically works but.
command = 'ping ' + '-n '+ str(count) + ' -l ' +
str(size) + ' ' + str(node)
print command
p = subprocess.Popen(command, stdin=subprocess.PIPE,
I am trying to use subprocess - it basically works but.
command = 'ping ' + '-n '+ str(count) + ' -l ' +
str(size) + ' ' + str(node)
print command
p = subprocess.Popen(command, stdin=subprocess.PIPE,
On 10/7/07, jorma kala <[EMAIL PROTECTED]> wrote:
> from subprocess import *
>
> p1 = Popen(["dir"], stdout=PIPE)
> output = p1.communicate()[0]
>
>
> But I get a WindowsError : [Error 2] File Not Found
Tim answered your actual question, but why are you doing this in the
first place? The Py
jorma kala wrote:
> I get an error that I don't understand when using the subprocess module
> on Windows.
> I guess I'm missing out something very basic.
> For instance, to execute and capture the output of the ms-dos dir
> command, I tried the following:
>
> from subprocess import *
>
> p1 = P
Hi,
I get an error that I don't understand when using the subprocess module on
Windows.
I guess I'm missing out something very basic.
For instance, to execute and capture the output of the ms-dos dir command, I
tried the following:
from subprocess import *
p1 = Popen(["dir"], stdout=PIPE)
outp
Hi,
Been there - try looking at:
http://groups.google.com/group/comp.lang.python/browse_frm/thread/f2cb83e948326ff5/d69feabbfc940b01?q=uri.nix&rnum=2#d69feabbfc940b01
Cheers,
Uri
--
http://mail.python.org/mailman/listinfo/python-list
On 23.06.2006 23:12:02, "3c273" wrote:
>"madpython" <[EMAIL PROTECTED]> wrote in message
>news:[EMAIL PROTECTED]
>> playing with subprocess.Popen on Windows I stumbled into the following
>> problem:
>> Python 2.4.3 (#69, Mar 29 2006, 17:35:34)
>
"madpython" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> playing with subprocess.Popen on Windows I stumbled into the following
> problem:
> Python 2.4.3 (#69, Mar 29 2006, 17:35:34)
>
> IDLE 1.1.3
>
> >>> import subprocess
>
playing with subprocess.Popen on Windows I stumbled into the following
problem:
Python 2.4.3 (#69, Mar 29 2006, 17:35:34)
IDLE 1.1.3
>>> import subprocess
>>> p1=subprocess.Popen("c:\\asd.bat") #works OK
>>> p2=subprocess.Popen("c:\\asd.bat",stdou
15 matches
Mail list logo
