Matt Joiner anacro...@gmail.com added the comment:
Two reasons: The pipes module is Unix only, but pipes.quote is useful on all
platforms. Secondly pipes.quote pertains to shell command-lines, this is also
the domain of shlex which already cross platform. In pipes, an import
shlex.quote would
Éric Araujo mer...@netwok.org added the comment:
Why do you want to move quote from pipes to shlex? The function is available,
the issue here is lack of documentation.
--
stage: - unit test needed
type: feature request -
___
Python tracker
Changes by Éric Araujo mer...@netwok.org:
--
stage: unit test needed - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9723
___
___
Matt Joiner anacro...@gmail.com added the comment:
I agree, I discovered this function (pipes.quote) only through recommendation
here:
http://stackoverflow.com/questions/4748344/whats-the-reverse-of-shlex-split
I suggest that it be added to shlex, perhaps as shlex.quote. While the quoting
Éric Araujo mer...@netwok.org added the comment:
Eric referred to this thread:
http://mail.python.org/pipermail/stdlib-sig/2010-May/thread.html
--
nosy: +eric.araujo
versions: -Python 2.5, Python 2.6, Python 3.3
___
Python tracker
New submission from Brandon Craig Rhodes bran...@rhodesmill.org:
The only way to safely build shell command lines from inside of Python — which
is necessary when sending commands across SSH, since that behaves like
os.system() rather than like subprocess.call() — is to use the wonderful
Eric Smith e...@trueblade.com added the comment:
I think you mean pipe.quote in your message, not pipe.call. The subject looks
correct.
I'm not sure pipes is the best place for this, but I agree it should probably
be documented in older versions. It seems to me we've had this discussion
