Miles Kaufmann mile...@umich.edu writes:
I would recommend avoiding shell=True whenever possible. It's used in
the examples, I suspect, to ease the transition from the functions
being replaced, but all it takes is for a filename or some other input
to unexpectedly contain whitespace or a
On Fri, Aug 21, 2009 at 2:08 AM, Ben Finneyben+pyt...@benfinney.id.au wrote:
snip
How can I take a string that is intended to be part of a command line,
representing multiple arguments and the shell's own escape characters as
in the above example, and end up with a sane command argument list
Ben Finney wrote:
Miles Kaufmann mile...@umich.edu writes:
I would recommend avoiding shell=True whenever possible. It's used in
the examples, I suspect, to ease the transition from the functions
being replaced, but all it takes is for a filename or some other input
to unexpectedly contain
Jean-Michel Pichavant jeanmic...@sequans.com writes:
Can someone explain the difference with the shell argument ? giving
for instance an example of what True will do that False won't.
The ‘shell’ argument to the ‘subprocess.Popen’ constructor specifies
whether the command-line should be
Chris Rebert c...@rebertia.com writes:
module shlex — Simple lexical analysis
New in version 1.5.2.
The shlex class makes it easy to write lexical analyzers for simple
syntaxes resembling that of the Unix shell.
Exactly what I needed:
import shlex
user_configured_args = --baz 'crunch
Ben Finney wrote:
Jean-Michel Pichavant jeanmic...@sequans.com writes:
Can someone explain the difference with the shell argument ? giving
for instance an example of what True will do that False won't.
The ‘shell’ argument to the ‘subprocess.Popen’ constructor specifies
whether the
Rick King rickbk...@comcast.net writes:
shlex doesn't handle unicode input though, so, in general, it's not a
good solution.
Argh. Is there a Python bug tracker number for fixing that? Or is there
a better solution?
--
\ “Pinky, are you pondering what I'm pondering?” “I think so, |
On Fri, Aug 21, 2009 at 3:55 PM, Ben Finneyben+pyt...@benfinney.id.au wrote:
Rick King rickbk...@comcast.net writes:
shlex doesn't handle unicode input though, so, in general, it's not a
good solution.
Argh. Is there a Python bug tracker number for fixing that?
Indeed there is:
