Series of patches for upstream consideration

[Kristoffer Grönlund]

Hi,

I have a set of patches that I would like to submit for inclusion upstream.

It seems to me that the easiest way to submit these is to give access to my git tree with the patches applied:

https://github.com/krig/parallel-ssh/commits/upstream-submission

The patches are as follows (in roughly increasing order of complexity):

1. Remove shebangs from library files:

    These files are distributed as part of a python module, but have the shebang of an executable script. Maybe not the most critical issue but I was getting a warning on this when packaging for openSUSE and it was a trivial fix.

2. Add quiet option:

    Adds a -q flag which suppresses informational output from pssh.

3. Fix order of command statuses returned by the Manager:

    When returning the exit status codes, the order of statuses in the list depends on the order in which the tasks completed, not the order in which they were supplied. This makes it difficult to match exit status to individual task. This patch makes sure that the lists are sorted in the same way.

4. test: Teardown code was never called:

    In the test suite, the name of the tearDown function was incorrectly spelled as teardown. This means that the unittest framework never actually calls the teardown code, so it never gets run. The patch corrects this.

5. Add an explicit API entrypoint:

   This patch adds an api module to pssh, to enable greater control over pssh when used as a library. 

   A larger example of use can be found here: https://github.com/crmsh/crmsh/blob/master/modules/scripts.py

   The test/api.py test suite has some smaller examples of API use.

Comments are very welcome!

Thanks,

Kristoffer