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 Vitali Lovich
Recipients Vitali Lovich
Date 2015-07-10.18:35:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436553329.08.0.818798657966.issue24607@psf.upfronthosting.co.za>
In-reply-to
Content
The subprocess module provides a good foundation of basic functionality.  However, anything moderately complex becomes cumbersome to write.  Additionally, it has pitfalls that people frequently overlook.

People then often either resort to hand-rolling their own abstraction on top of it, use the library incorrectly, or just use shell scripts if the predominant action is to stitch things together.

I have seen great success at avoiding having to write shell-scripts & using the sh package. What once would have been written as shell-scripts now can be written very naturally using sh in a more maintainable & reusable manner.

I think sh being part of the standard library would be a great addition & make python even more compelling as a replacement for shell scripts.  Having sh be part of the python library also ensures that the `with` syntax could be done in a comprehensive thread-safe manner.

https://pypi.python.org/pypi/sh
http://amoffat.github.com/sh
History
Date User Action Args
2015-07-10 18:35:29Vitali Lovichsetrecipients: + Vitali Lovich
2015-07-10 18:35:29Vitali Lovichsetmessageid: <1436553329.08.0.818798657966.issue24607@psf.upfronthosting.co.za>
2015-07-10 18:35:29Vitali Lovichlinkissue24607 messages
2015-07-10 18:35:28Vitali Lovichcreate