[issue3548] subprocess.pipe function

Mike Frysinger added the comment: this would have been nice to have more than once in my personal projects, and in build/infra tooling for Chromium OS. our alternatives so far have been the obvious ones: use subprocess.run to capture & return the output, then manually feed that as the input

[issue3548] subprocess.pipe function

Changes by desbma : -- nosy: +desbma ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mai

[issue3548] subprocess.pipe function

Matheus Vieira Portela added the comment: Sure. I'll leave this issue for a while before others can emit their opinions. -- ___ Python tracker ___

[issue3548] subprocess.pipe function

R. David Murray added the comment: Exactly like the string pipes API, but cmd would be a list of arguments instead of a string. That would then become the argument list to the subprocess stage. It is an interesting question whether we'd want to allow mixing stage types. I'd say no (at least

[issue3548] subprocess.pipe function

Matheus Vieira Portela added the comment: Oh, I see... The pipes module uses os.system and os.popen to execute commands under a "/bin/sh" environment. So you are proposing to re-implement it with subprocess in order to execute commands without shell and, also, extend by accepting argv-style pa

[issue3548] subprocess.pipe function

R. David Murray added the comment: No, I'm talking about https://docs.python.org/3/library/pipes.html -- ___ Python tracker ___ ___ Pyt

[issue3548] subprocess.pipe function

Matheus Vieira Portela added the comment: Let me check whether I understood you suggestion... What you are saying is that it is already possible to pipeline shell commands through subprocess, such as in the following line? subprocess.call('ls -l | grep Music', shell=True) However, this requir

[issue3548] subprocess.pipe function

R. David Murray added the comment: Thanks for being willing to work on it. If what is wanted is a way to pipeline shell commands, Python already has that functionality in the pipes module. So the interesting thing here would be pipelining *non* shell commands, to avoid the shell exploits that

[issue3548] subprocess.pipe function

Matheus Vieira Portela added the comment: I just found this open issue and I can work on it. What is left to do before closing it? -- nosy: +matheus.v.portela ___ Python tracker

[issue3548] subprocess.pipe function

Changes by Miki Tebeka : -- nosy: -tebeka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue3548] subprocess.pipe function

Antoine Pitrou added the comment: I think this would be more useful if you could pass an optional input string (as in communicate()) and if it returned a (stdout, stderr) tuple. Or perhaps even a (return code, stdout, stderr) tuple; alternately, non-zero return codes could raise an exception.

[issue3548] subprocess.pipe function

Éric Araujo added the comment: pipe.patch looks interesting to me. I would replace **kwargs with a keyword-only argument named stderr, since that’s the only key used. This requires more tests and docs. -- nosy: +eric.araujo ___ Python tracker

[issue3548] subprocess.pipe function

Anh Hai Trinh added the comment: I've written a package which can do this with arbitrary redirection in all subcommands (and some more). You can, for example, do this: >>> Pipe(Sh('echo -n foo >&2', {2: 1}), Sh('cat; echo ERROR >&2', {2: os.devnull})).capture(1).read() 'foo' The pac

[issue3548] subprocess.pipe function

Changes by Ernesto Menéndez : -- nosy: +Netto ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue3548] subprocess.pipe function

Changes by Georg Brandl : -- versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue3548] subprocess.pipe function

Legoll Vincent <[EMAIL PROTECTED]> added the comment: On Mon, Sep 1, 2008 at 5:13 PM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote: > Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > > Vincent, > GPL licenced code is incompatible with the inclusion into python. > And if I am correc

[issue3548] subprocess.pipe function

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Vincent, GPL licenced code is incompatible with the inclusion into python. And if I am correct, you should sign a contributor agreement. Then the licence text is not necessary. -- nosy: +amaury.forgeotdarc _

[issue3548] subprocess.pipe function

Vincent Legoll <[EMAIL PROTECTED]> added the comment: - Added "shut pylint up" comment for ** keyword expansion - Added Copyright & license header Added file: http://bugs.python.org/file11330/pipeline.py ___ Python tracker <[EMAIL PROTECTED]>

[issue3548] subprocess.pipe function

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- priority: -> normal versions: +Python 2.7, Python 3.1 -Python 2.6, Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3548] subprocess.pipe function

Vincent Legoll <[EMAIL PROTECTED]> added the comment: Here's a clean version with doc & test enjoy ! Added file: http://bugs.python.org/file11263/pipeline.py ___ Python tracker <[EMAIL PROTECTED]> __

[issue3548] subprocess.pipe function

Vincent Legoll <[EMAIL PROTECTED]> added the comment: Hello, I was searching for a bug in subprocess module when I saw your patch. I was implementing the exact same functionality and mixed some of your ideas in what I use now, which is attached... Feel free to use it -- nosy: +vincent

[issue3548] subprocess.pipe function

Miki Tebeka <[EMAIL PROTECTED]> added the comment: Not sure about the name, maybe "chain" will be better? ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3548] subprocess.pipe function

New submission from Miki Tebeka <[EMAIL PROTECTED]>: Attached is a patch that add "pipe" command to the "subprocess" module. pipe(["ls"], ["grep", "test_"]) will return the output of "ls | grep test_". -- components: Library (Lib) files: pipe.patch keywords: patch messages: 71062 nosy: