Re: [Tutor] subprocess module: when to _NOT_ use shell=True

Thank you "Eryksun" and "EikeWek" for your responses. It is this sort of thing that begins to pull one out of the newbie into the intermediate category. I'm grateful. alex > I've not found anywhere a clear explanation of when not to set shell=True. > If the command line must be interpreted by the

Re: [Tutor] subprocess module: when to _NOT_ use shell=True

On Sunday 10.03.2013 09:56:26 aklei...@sonic.net wrote: > I've not found anywhere a clear explanation of when not to set shell=True. > If the command line must be interpreted by the shell then clearly this > must be set. So the question that comes up is why not set it always? Because ``shell=True`

Re: [Tutor] subprocess module: when to _NOT_ use shell=True

On Sun, Mar 10, 2013 at 12:56 PM, wrote: > I've not found anywhere a clear explanation of when not to > set shell=True. If the command line must be interpreted by > the shell then clearly this must be set. So the question > that comes up is why not set it always? Using the shell can be a securit

[Tutor] subprocess module: when to _NOT_ use shell=True

I've not found anywhere a clear explanation of when not to set shell=True. If the command line must be interpreted by the shell then clearly this must be set. So the question that comes up is why not set it always? In an effort to investigate, I came up with the following script that indicates tha