This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Netto, aht, amaury.forgeotdarc, eric.araujo, matheus.v.portela, pitrou, r.david.murray, vincent.legoll, vlegoll
Date 2015-08-25.14:03:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440511433.21.0.315958060184.issue3548@psf.upfronthosting.co.za>
In-reply-to
Content
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 using a shell pipeline invites.

The pipes module already has a worked out API, so perhaps it would be useful to see about re-implementing pipe's command execution using subprocess, and expand the API to allow for argv style command specification that would be fed to subprocess using the default shell=False.  This would also presumably allow pipes to be used when there's no bash shell available.

The downside is that we might break current uses of pipes if we replace the shell version of the pipelining with subprocess shell=True, while using subprocess only if the command specifications are argv lists would result in code with a split personality.  But if I were working on it I'd experiment with that approach to see if it made sense.

Other core devs may have other opinions on this :)
History
Date User Action Args
2015-08-25 14:03:53r.david.murraysetrecipients: + r.david.murray, amaury.forgeotdarc, pitrou, vlegoll, eric.araujo, vincent.legoll, aht, Netto, matheus.v.portela
2015-08-25 14:03:53r.david.murraysetmessageid: <1440511433.21.0.315958060184.issue3548@psf.upfronthosting.co.za>
2015-08-25 14:03:53r.david.murraylinkissue3548 messages
2015-08-25 14:03:52r.david.murraycreate