Insufficient error reporting

[spooning]

Originally submitted to Google Code by SonOfLilit on 30 Oct 2008

When something goes wrong in the SSH session (as simple as telling it to
copy a file that doesn't exist) there is no reporting and no crashing.

This makes it very hard to figure out what went wrong when a test failed,
and in some cases even creates false positives.

Is there a plan to improve exception throwing and error reporting?

For one, I would advise enabling the paramiko log (or adding a keyword to
enable it):

def __init__(self, host, port=22):
    paramiko.util.log_to_file('paramiko.log')

Above that, there are loads of error handling code that has to be written.
You may assign it to me, but I would probably be very slow about it as I
have many other roles at my company.

p.s. How do I mark an issue as "Enhancement"?

[spooning]

Originally submitted to Google Code by @yanne on 31 Oct 2008

This is a valid issue in case of file transfers. Get File and Put File should
probably fail if the source file does not exist. Which other error handling code do
you think is missing? The execute command and write/read keywords can't really do any
error handling.

Enabling paramiko logging is a good idea.

To change the type of issue, you can remove the Type-Defect label and insert
Type-Enhancement instead.

[spooning]

Originally submitted to Google Code by @yanne on 3 Nov 2008

Get File and Put File now fail if source files do not exist, in r41

[spooning]

Originally submitted to Google Code by @yanne on 7 Nov 2008

Enabled logging SSH traffic to file, in r42.
This currently works only with Python.